This repository has been archived by the owner on Oct 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 26
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
Build #1
|
jupierce
force-pushed
the
avoid_git_zero_prefix
branch
2 times, most recently
from
November 1, 2021 16:42
4a96e7f
to
c8a1f27
Compare
jupierce
changed the title
Strip leading zero whenever constructing/checking semver
Prevent leading zero in nvr semver
Nov 1, 2021
Wondering if it shouldn't just be |
Build #2
|
jupierce
force-pushed
the
avoid_git_zero_prefix
branch
from
November 1, 2021 16:54
c8a1f27
to
09e3509
Compare
jupierce
force-pushed
the
avoid_git_zero_prefix
branch
from
November 1, 2021 16:58
09e3509
to
7d4f30a
Compare
Build #3
|
Think this does what says on the tin, yet not comfortable enough for a /lgtm as I have very little idea who or what depends on the current scheme. Should this first be limited to 4.10 at first and be subject to backports? Or we just roll with it? Should this be documented in all releases with a changelog? |
Build #4
|
Just wondering if there needs to be a test added wrt continuing to recognize the existing |
vfreex
approved these changes
Nov 2, 2021
vfreex
added a commit
to vfreex/elliott
that referenced
this pull request
Nov 4, 2021
See openshift-eng/doozer#527. There's no code in Elliott using the git commit hash. This PR just updates comments and tests to keep consistency with Doozer.
No code in Elliott is affected by the new format. But I created this PR openshift-eng/elliott#243 anyway to update examples, comments, and tests to keep consistency. |
vfreex
added a commit
to vfreex/elliott
that referenced
this pull request
Nov 11, 2021
See openshift-eng/doozer#527. There's no code in Elliott using the git commit hash. This PR just updates comments and tests to keep consistency with Doozer.
vfreex
added a commit
to vfreex/doozer
that referenced
this pull request
Nov 19, 2021
e810dcb Permit assemblies to use custom rhcos builds The RHCOS pipeline, when configured for a custom build, will bucket the resulting metadata files in s3 in a directory suffixed with `-custom`. In order to for assemblies to use custom RHCOS builds, we must try to find metadata in either the standard location or `-custom` location. 0a4d5ca [ART-3109] Use container.yaml to apply floating tags (openshift-eng#524) e3e6315 ART-3437: Make bundle tag names configurable 36b3291 Prevent leading zero in semver (openshift-eng#527) 57af5c8 Revert "make bundle tag names configurable (openshift-eng#532)" (openshift-eng#533) 3a14f91 make bundle tag names configurable (openshift-eng#532) 3c16d82 Allow olm-bundle:print to skip when builds are missing b3cc4c3 We are in the future 69e613e Update code to work with flexmock 0.11 4107d82 ART-2519 add check upstreampulls function (openshift-eng#488) 56325c6 bump-doozer: add annotated tag
ashwindasr
pushed a commit
to ashwindasr/art-tools
that referenced
this pull request
Jul 19, 2023
See openshift-eng/doozer#527. There's no code in Elliott using the git commit hash. This PR just updates comments and tests to keep consistency with Doozer.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The semver standard prevents numeric elements of the pre-release portion of a version from starting with
0
. This means that doozer could rarely create invalid semvers like.git.0123456
. We will change to be.g0123456
so these fields are always non-numeric.