-
Notifications
You must be signed in to change notification settings - Fork 14
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
Release v0.12.1-alpha.1 #193
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3scale-robot
added
kind/feature
Categorizes issue or PR as related to a new feature.
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next sprint.
needs-size
Indicates a PR or issue lacks a `size/foo` label and requires one.
labels
May 30, 2023
3scale-robot
added
size/L
Requires few days to complete the PR or the issue.
and removed
needs-size
Indicates a PR or issue lacks a `size/foo` label and requires one.
labels
May 30, 2023
slopezz
reviewed
May 30, 2023
slopezz
reviewed
May 30, 2023
roivaz
force-pushed
the
release-v0.12.1-alpha.1
branch
from
May 30, 2023 14:16
3a65ab5
to
c7b70a8
Compare
raelga
approved these changes
May 30, 2023
raelga
approved these changes
May 30, 2023
raelga
approved these changes
May 30, 2023
LGTM label has been added. Git tree hash: c04d7b0399d320568487e2b9504a25eb6724f735
|
slopezz
reviewed
May 30, 2023
roivaz
force-pushed
the
release-v0.12.1-alpha.1
branch
from
May 30, 2023 15:01
c7b70a8
to
380896e
Compare
/lgtm |
LGTM label has been added. Git tree hash: ea0559662fb9d4b5dcc431749861ec29c9b3a407
|
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: roivaz The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
3scale-robot
added
the
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
label
May 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
kind/bug
Categorizes issue or PR as related to a bug.
kind/feature
Categorizes issue or PR as related to a new feature.
lgtm
Indicates that a PR is ready to be merged.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next sprint.
size/L
Requires few days to complete the PR or the issue.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR migrates the marin3r upstream catalog to the file based catalog format. A couple of important things:
I have cleaned up all alpha bundles from the catalog (there were a lot of them) and added the
skipRanges
option to the alpha catalog so any alpha bundle will be directly upgraded to its corresponding stable bundle. For examplemarin3r.v0.11.0-alpha.5
will be upgraded directly tomarin3r.v0.11.0
instead of installing all the alpha releases in between.I have included v0.12.0 in the skipped range for v0.11.1 so it's never installed, as it contains the now infamous upgrade bug. I added a comment in the alpha channel to clarify this.
This PR just updates the alpha channel, I'll test v0.12.1-alpha.1 in staging and then upgrade the stable channel and re-test the upgrade path in staging.
/kind feature
/kind bug
/priority important-soon
/assign