chore(deps): update dependency defenseunicorns/uds-cli to v0.19.0 #250
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/defenseunicorns-uds-cli-0.x
branch
from
b0011a0 to
e37825e
Compare
There was a problem hiding this comment.
i'm on this version locally, but would defer to @JoeHCQ1 and @jacobbmay
|
@MxNxPx , this one is a bit more tricky. We're only promising to work with a particular version of the UDS CLI, the same one which is in the build image we're using to run the UDS commands in the UDS Tasks file. Reason for it: @jacobbmay would have to weigh in here for the specifics. I recall him saying we had problems arise earlier on that resulted from mismatched UDS CLI version so we're using the build image to specify the agree-able UDS CLI version. Problems it causes:
|
|
The reason for using a build-harness image wasn't because of uds-cli issues. It was other OS dependencies that some after deploy scripts use that didn't have same options available in a customer environment's CI image which caused failures. The purpose of the image is to provide a consistent deployment environment and eliminate "works on my machine" scenarios between us and customer environments. It eliminates needing to make assumptions about a deployment environment since we can tell users to just use that image for a guaranteed working deployment container. Regarding the commands being a bit more complicated to look at, the tasks are set up so we can spin up the container locally. In a real deployment the image would just be selected as the runner image and UDS commands would be configured in the job scripts. No need to build something that works like our deploy tasks. |
| datasource | package | from | to | | ----------- | ----------------------- | ------- | ------- | | github-tags | defenseunicorns/uds-cli | 0.17.0 | 0.19.0 | | github-tags | defenseunicorns/uds-cli | v0.17.0 | v0.19.0 | | github-tags | defenseunicorns/uds-cli | v0.16.0 | v0.19.0 |
JoeHCQ1
force-pushed
the
renovate/defenseunicorns-uds-cli-0.x
branch
from
178dc33 to
dced2b8
Compare
Edited/Blocked NotificationRenovate 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. |
|
Updated to the latest build harness because it has UDS CLI 0.19.0 https://github.com/defenseunicorns/build-harness/blob/2.0.46/.tool-versions#L34 |
This PR contains the following updates:
0.17.0->0.19.0v0.17.0->v0.19.0v0.16.0->v0.19.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
defenseunicorns/uds-cli (defenseunicorns/uds-cli)
v0.19.0Compare Source
What's Changed
NOTE:
uds-uicommand has been removed. The team is reevaluating how the CLI should interact with the Runtime component, and decided to remove the feature for now. (https://github.com/defenseunicorns/uds-cli/pull/1010)d060b6dby @renovate in https://github.com/defenseunicorns/uds-cli/pull/95039370e3by @renovate in https://github.com/defenseunicorns/uds-cli/pull/959f66d83cby @renovate in https://github.com/defenseunicorns/uds-cli/pull/9602a92d20by @renovate in https://github.com/defenseunicorns/uds-cli/pull/100196b6254by @renovate in https://github.com/defenseunicorns/uds-cli/pull/1005New Contributors
Full Changelog: defenseunicorns/uds-cli@v0.18.0...v0.19.0
v0.18.0Compare Source
What's Changed
New Contributors
Full Changelog: defenseunicorns/uds-cli@nightly-unstable...v0.18.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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.