-
-
Notifications
You must be signed in to change notification settings - Fork 5
Feature/tools versioning #122
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
base: main
Are you sure you want to change the base?
Feature/tools versioning #122
Conversation
|
Let's resolve what we want to accomplish in #111 first. |
| git commit -m "Release supply_chain_tools v${VERSION}" | ||
|
|
||
| # 3. Push supply_chain_tools release tag | ||
| git tag "supply_chain_tools-v${VERSION}" "HEAD" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
git tag "tools-${VERSION}" "HEAD"
| GIT_COMMITTER_EMAIL: "${{ github.actor_id }}+${{ github.actor }}@users.noreply.github.com" | ||
| run: | | ||
| # 1. Download `buildozer` | ||
| curl -o "${RUNNER_TEMP}/buildozer" -L "https://github.com/bazelbuild/buildtools/releases/download/v7.3.1/buildozer-linux-amd64" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Buildozer is overkill. We should be able to rewrite the version with sed.
|
@ankushkumar11 Any thoughts. We do want to have distinct releases for each sup-component of the project, but let's ahve a worked out plan first. in #111 |
Add separate release workflow for supply_chain_tools
This allows supply_chain_tools to be released independently of the main supply-chain
project and package_metadata, providing users with focused releases for just the
tools functionality including gather_metadata and sbom utilities.