Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update uds to v0.8.1 #141

Merged
merged 4 commits into from
Feb 7, 2024
Merged

chore(deps): update uds to v0.8.1 #141

merged 4 commits into from
Feb 7, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 29, 2024

Mend Renovate

This PR contains the following updates:

Package Update Change
defenseunicorns/uds-cli minor 0.6.2 -> 0.8.1

Release Notes

defenseunicorns/uds-cli (defenseunicorns/uds-cli)

v0.8.1

Compare Source

What's Changed

Full Changelog: defenseunicorns/uds-cli@v0.8.0...v0.8.1

v0.8.0

Compare Source

What's Changed

New Contributors

Full Changelog: defenseunicorns/uds-cli@v0.7.0...v0.8.0

v0.7.0

Compare Source

What's Changed

Full Changelog: defenseunicorns/uds-cli@v0.6.2...v0.7.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link
Contributor

@mjnagel mjnagel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haven't done a full evaluation/test but I think our bundle publishing might need some updates to handle the new architecture publishing (multi-arch)?

@renovate renovate bot changed the title chore(deps): update uds to v0.7.0 chore(deps): update uds to v0.8.0 Feb 6, 2024
| datasource  | package                 | from  | to    |
| ----------- | ----------------------- | ----- | ----- |
| github-tags | defenseunicorns/uds-cli | 0.6.2 | 0.8.1 |
@renovate renovate bot changed the title chore(deps): update uds to v0.8.0 chore(deps): update uds to v0.8.1 Feb 7, 2024
Copy link
Contributor Author

renovate bot commented Feb 7, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@renovate renovate bot requested a review from a team as a code owner February 7, 2024 03:21
@mjnagel
Copy link
Contributor

mjnagel commented Feb 7, 2024

@zachariahmiller / @jeff-mccoy if you have a chance to take a look, not sure if either of you have a preference on our latest tag. With the new uds-cli version arch is handled the same way as zarf so it doesn't make sense to use archfor "latest" anymore imo. I switched it to literal latest which feels right, but we don't reference it in our docs anywhere...so not sure if we should just drop that extra tag creation? Or switch the quickstart to reference latest?

@zachariahmiller
Copy link
Contributor

Don't feel strongly either way on keeping or removing the secondary tag.

If we are gonna keep the secondary tag for the demo bundle I think latest is the most clear and would mean we don't need to touch the documentation on how to consume that bundle every time we do a release.

It also seems the most obvious and in line with what someone might expect when going to try something (like docker run image:latest) in a quickstart.

On the other hand, if there is a strong aversion to the latest tag I think we can drop it. However,I don't think the rationale there would be particularly relevant to a demo artifact.

@zachariahmiller zachariahmiller merged commit fa79065 into main Feb 7, 2024
7 checks passed
@zachariahmiller zachariahmiller deleted the renovate/uds branch February 7, 2024 20:00
jeff-mccoy pushed a commit that referenced this pull request Feb 7, 2024
🤖 I have created a release *beep* *boop*
---


##
[0.11.0](v0.10.0...v0.11.0)
(2024-02-07)


### Features

* added initial oscal files
([#145](#145))
([9600d5f](9600d5f))


### Bug Fixes

* network policy to allow metrics-server ingress
([#148](#148))
([f1d434a](f1d434a))


### Miscellaneous

* **deps:** update grafana to v7.2.5
([#136](#136))
([a271270](a271270))
* **deps:** update grafana to v7.3.0
([#142](#142))
([5e960c0](5e960c0))
* **deps:** update loki
([#131](#131))
([61250b0](61250b0))
* **deps:** update pepr to v0.24.1
([#134](#134))
([6474a1c](6474a1c))
* **deps:** update prometheus-stack
([#128](#128))
([625622a](625622a))
* **deps:** update uds to v0.8.1
([#141](#141))
([fa79065](fa79065))
* **deps:** update zarf to v0.32.2
([#133](#133))
([91502c6](91502c6))
* readme updates & use UDS CLI for zarf
([#137](#137))
([21de0ce](21de0ce))
* renovate updates
([#140](#140))
([b71a013](b71a013))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
robmcelvenny pushed a commit to owen-grady/uds-core-slim-dev that referenced this pull request Jun 3, 2024
🤖 I have created a release *beep* *boop*
---


##
[0.11.0](defenseunicorns/uds-core@v0.10.0...v0.11.0)
(2024-02-07)


### Features

* added initial oscal files
([#145](defenseunicorns/uds-core#145))
([9600d5f](defenseunicorns/uds-core@9600d5f))


### Bug Fixes

* network policy to allow metrics-server ingress
([#148](defenseunicorns/uds-core#148))
([f1d434a](defenseunicorns/uds-core@f1d434a))


### Miscellaneous

* **deps:** update grafana to v7.2.5
([#136](defenseunicorns/uds-core#136))
([a271270](defenseunicorns/uds-core@a271270))
* **deps:** update grafana to v7.3.0
([#142](defenseunicorns/uds-core#142))
([5e960c0](defenseunicorns/uds-core@5e960c0))
* **deps:** update loki
([#131](defenseunicorns/uds-core#131))
([61250b0](defenseunicorns/uds-core@61250b0))
* **deps:** update pepr to v0.24.1
([#134](defenseunicorns/uds-core#134))
([6474a1c](defenseunicorns/uds-core@6474a1c))
* **deps:** update prometheus-stack
([#128](defenseunicorns/uds-core#128))
([625622a](defenseunicorns/uds-core@625622a))
* **deps:** update uds to v0.8.1
([#141](defenseunicorns/uds-core#141))
([fa79065](defenseunicorns/uds-core@fa79065))
* **deps:** update zarf to v0.32.2
([#133](defenseunicorns/uds-core#133))
([91502c6](defenseunicorns/uds-core@91502c6))
* readme updates & use UDS CLI for zarf
([#137](defenseunicorns/uds-core#137))
([21de0ce](defenseunicorns/uds-core@21de0ce))
* renovate updates
([#140](defenseunicorns/uds-core#140))
([b71a013](defenseunicorns/uds-core@b71a013))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants