Skip to content

Conversation

@ishitasequeira
Copy link
Collaborator

@ishitasequeira ishitasequeira commented Jan 27, 2025

Update release process to create a separate tag for registry-scanner.

Currently, keeping the release version of registry-scanner same as image updater. Let me know if we need to change this version matching for image-updater and registry-scanner.

Updated to have separate release of registry-scanner

@ishitasequeira ishitasequeira changed the title Update release script Update release process to create a separate tag for registry-scanner Jan 27, 2025
@codecov-commenter
Copy link

codecov-commenter commented Jan 27, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 62.57%. Comparing base (016f8e2) to head (308b598).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1022   +/-   ##
=======================================
  Coverage   62.57%   62.57%           
=======================================
  Files          15       15           
  Lines        2250     2250           
=======================================
  Hits         1408     1408           
  Misses        753      753           
  Partials       89       89           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ishitasequeira ishitasequeira marked this pull request as ready for review January 27, 2025 13:53
@chengfang
Copy link
Collaborator

I personally prefer to have the release files contained under registry-scanner itself. I guess pretty soon these 2 will diverge in versions. Then for image-updater, registry-scanner is just another dependency to manage.

# Create tag for registry-scanner
git tag "${NEW_TAG}"
git push "${REMOTE}" tag "${NEW_TAG}"

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we just name this file as create-release.sh since it just creates a release tag, without any PR?

echo "${TARGET_VERSION}" > VERSION

# Create tag for registry-scanner
git tag "${NEW_TAG}"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can create an annotated tag to include additional information about the tag?

# - run this script from repo root: ./hack/create-release-pr.sh [REMOTE]
# - merge the PR
# It will trigger the release workflow that would create release draft on github

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this script takes 2 args, so the above comments need updating to reflect that. Also no PR is involved.

set -o pipefail

if test "${TARGET_VERSION}" = ""; then
echo "USAGE: $0 <version>" >&2
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the usage should warn about 2 args

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have kept the remote as an optional parameter defaulting to origin.

Signed-off-by: Ishita Sequeira <[email protected]>
Signed-off-by: Ishita Sequeira <[email protected]>
@chengfang chengfang merged commit 4a3aa80 into argoproj-labs:master Jan 31, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants