implemented exit-gate - #546
Open
123-komal wants to merge 1 commit into
Open
Conversation
123-komal
force-pushed
the
oss-exit-gate
branch
from
October 9, 2025 16:06
3cba783 to
e825080
Compare
123-komal
force-pushed
the
oss-exit-gate
branch
from
October 9, 2025 16:14
e825080 to
5e5be27
Compare
123-komal
force-pushed
the
oss-exit-gate
branch
3 times, most recently
from
February 10, 2026 06:21
1c1c1c3 to
0386edb
Compare
123-komal
force-pushed
the
oss-exit-gate
branch
2 times, most recently
from
February 10, 2026 06:56
348cc16 to
ebe32eb
Compare
updated Implemented exit gate
123-komal
force-pushed
the
oss-exit-gate
branch
from
February 11, 2026 09:02
ebe32eb to
d6ccb6c
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 change refactors the build process to improve artifact security and provenance.
Key Changes:
Maven artifact building and GPG signing for releases are now performed within GCB.
Release artifacts, signatures, and build metadata are staged in a designated bucket.
This new process enhances the security and verifiability of the build supply chain.