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

feat(versioning): add versioning scheme for glasskube package manager #29506

Merged
merged 2 commits into from
Jun 10, 2024

Conversation

kosmoz
Copy link
Contributor

@kosmoz kosmoz commented Jun 7, 2024

Changes

This PR adds a new versioning scheme used by the Glasskube package manager.

Context

See #29322

Documentation (please check one with an [x])

  • I have updated the documentation, or
  • No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

  • Code inspection only, or
  • Newly added/modified unit tests, or
  • No unit tests but ran on a real repository, or
  • Both unit tests + ran on a real repository

Signed-off-by: Jakob Steiner <jakob.steiner@glasskube.eu>
rarkins
rarkins previously approved these changes Jun 7, 2024
@rarkins rarkins enabled auto-merge June 7, 2024 15:14
auto-merge was automatically disabled June 10, 2024 08:47

Head branch was pushed to by a user without write access

@rarkins rarkins enabled auto-merge June 10, 2024 10:57
@rarkins rarkins added this pull request to the merge queue Jun 10, 2024
Merged via the queue into renovatebot:main with commit 4b44b30 Jun 10, 2024
37 of 51 checks passed
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 37.401.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

kosmoz added a commit to kosmoz/renovate that referenced this pull request Jun 12, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants