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

Bump open-component-model/ocm/ocm.software/ocmcli/ocmcli-image from 0.18.0 to 0.19.0 #1105

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 23, 2024

Bumps open-component-model/ocm/ocm.software/ocmcli/ocmcli-image from 0.18.0 to 0.19.0.

Release notes

Sourced from open-component-model/ocm/ocm.software/ocmcli/ocmcli-image's releases.

v0.19.0

What's Changed

🚀 Features

🧰 Maintenance

⬆️ Dependencies

... (truncated)

Changelog

Sourced from open-component-model/ocm/ocm.software/ocmcli/ocmcli-image's changelog.

Release Process

General Information

In the Open Component Model organization, the main development is done on the main branch. Thus, the main branch is used to develop on the latest minor version.

The release process focuses on the creation of release/<major>.<minor> release branches and the generation of release tags based on these branches. Every release branch is used to permanently track the development of a specific minor release of the OCM project. Whenever there is a critical issue for a specific minor release, a patch is cherry-picked into the release branch and a new patch release for that given minor version is created.

The release branches are initially created from the main branch via the GitHub action Release Branch Creation.

A release is generated by calling a specific release GitHub Action. It is executed on the branch which should be released - regardless whether it is a patch or a minor release.

In any case, a pre-release may be created by specifying a pre-release suffix for the release action execution. This will lead (for most use cases) to the creation of a "Release Candidate" which can be tested and delivered to end users willing to test the new release.

Release Workflow

Diagram

gitGraph TB:
    commit id: "VERSION 0.17.0-dev"
    commit id: "feat: some feature"
    branch "releases/v0.17"
    commit tag: "v0.17.0-rc.1" type: REVERSE
    checkout main
    commit id: "fix: hotfix bug" type: HIGHLIGHT
    checkout releases/v0.17
    cherry-pick id: "fix: hotfix bug"
    commit tag: "v0.17.0-rc.2"
    branch "releases/v0.17.0"
    checkout "releases/v0.17.0"
    commit id: "VERSION 0.17.0" tag:"v0.17.0"
    checkout main
    commit id: "VERSION 0.18.0-dev"
</tr></table> 
Loading

... (truncated)

Commits
  • 7b3927d chore: rework release note handling (#1139)
  • 4205242 chore(documentation): How to publish winget packages. (#1138)
  • 17166ce chore(example): let's limit the listed versions (#1136)
  • 3465bb4 chore(github_actions): using now classic secret of OCM_CI_ROBOT (#1137)
  • 9033cb5 chore(signing): correct Fulcio service to correct address (#1135)
  • 3133edf chore(github_actions): push-to-winget: permissions: write-all (#1133)
  • f5a1cd2 chore: publish to website as other (#1126)
  • 88d3ead chore: update 'flake.nix' (#1129)
  • bd14400 chore(deps): bump the go group with 17 updates (#1127)
  • 0f25608 chore(deps): bump anchore/sbom-action from 0.17.7 to 0.17.8 in the ci group (...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [open-component-model/ocm/ocm.software/ocmcli/ocmcli-image](https://github.com/open-component-model/ocm) from 0.18.0 to 0.19.0.
- [Release notes](https://github.com/open-component-model/ocm/releases)
- [Changelog](https://github.com/open-component-model/ocm/blob/main/RELEASE_PROCESS.md)
- [Commits](open-component-model/ocm@v0.18...v0.19)

---
updated-dependencies:
- dependency-name: open-component-model/ocm/ocm.software/ocmcli/ocmcli-image
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file docker Pull requests that update Docker code labels Dec 23, 2024
@gardener-robot gardener-robot added the needs/review Needs review label Dec 23, 2024
@gardener-robot
Copy link

@dependabot[bot] Thank you for your contribution.

@gardener-robot gardener-robot added the size/xs Size of pull request is tiny (see gardener-robot robot/bots/size.py) label Dec 23, 2024
@ccwienk
Copy link
Member

ccwienk commented Jan 9, 2025

/hold ocm-cli 0.19.0 has a known regression / backwards-incompatible change w.r.t. normalisation. hence, we must skip 0.19.0, and remain on 0.18.0 as lkg, until either a patch-version of 0.19, or a greater minor-version of ocm-cli will be released

@gardener-robot gardener-robot added the reviewed/do-not-merge Has no approval for merging as it may break things, be of poor quality or have (ext.) dependencies label Jan 9, 2025
Copy link
Member

@ccwienk ccwienk left a comment

Choose a reason for hiding this comment

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

do not merge

@gardener-robot gardener-robot added the needs/changes Needs (more) changes label Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file docker Pull requests that update Docker code needs/changes Needs (more) changes needs/review Needs review reviewed/do-not-merge Has no approval for merging as it may break things, be of poor quality or have (ext.) dependencies size/xs Size of pull request is tiny (see gardener-robot robot/bots/size.py)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants