Skip to content

👷 Push tag after creating draft release#6818

Merged
dubzzz merged 2 commits into
mainfrom
claude/push-tags-draft-releases-RoE4N
Apr 4, 2026
Merged

👷 Push tag after creating draft release#6818
dubzzz merged 2 commits into
mainfrom
claude/push-tags-draft-releases-RoE4N

Conversation

@dubzzz

@dubzzz dubzzz commented Apr 4, 2026

Copy link
Copy Markdown
Owner

Description

The draft release creation via softprops/action-gh-release creates the
tag through the GitHub API, which doesn't trigger git push events. This
adds an explicit git tag + push step after the release is created, so
that downstream workflows listening for tag pushes can detect the tag.

Also switches persist-credentials to true so the GITHUB_TOKEN is
available for git push operations.

https://claude.ai/code/session_01NsbWgAUGTnBxikVhazo7hB

Fixes #issue-number

Checklist

Don't delete this checklist and make sure you do the following before opening the PR

  • I have a full understanding of every line in this PR — whether the code was hand-written, AI-generated, copied from external sources or produced by any other tool
  • I flagged the impact of my change (minor / patch / major) either by running pnpm run bump or by following the instructions from the changeset bot
  • I kept this PR focused on a single concern and did not bundle unrelated changes
  • I followed the gitmoji specification for the name of the PR, including the package scope (e.g. 🐛(vitest) Something...) when the change targets a package other than fast-check
  • I added relevant tests and they would have failed without my PR (when applicable)

The draft release creation via softprops/action-gh-release creates the
tag through the GitHub API, which doesn't trigger git push events. This
adds an explicit git tag + push step after the release is created, so
that downstream workflows listening for tag pushes can detect the tag.

Also switches persist-credentials to true so the GITHUB_TOKEN is
available for git push operations.

https://claude.ai/code/session_01NsbWgAUGTnBxikVhazo7hB
@changeset-bot

changeset-bot Bot commented Apr 4, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: fa7ad21

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@dubzzz dubzzz changed the title Push tag after creating draft release The draft release creation via softprops/action-gh-release creates the tag through the GitHub API, which doesn't trigger git push events. This adds an explicit git tag + push step after the release is created, so that downstream workflows listening for tag pushes can detect the tag. Also switches persist-credentials to true so the GITHUB_TOKEN is available for git push operations. https://claude.ai/code/session_01NsbWgAUGTnBxikVhazo7hB 👷 Push tag after creating draft release Apr 4, 2026
@pkg-pr-new

pkg-pr-new Bot commented Apr 4, 2026

Copy link
Copy Markdown
@fast-check/ava

npm i https://pkg.pr.new/@fast-check/ava@6818

fast-check

npm i https://pkg.pr.new/fast-check@6818

@fast-check/jest

npm i https://pkg.pr.new/@fast-check/jest@6818

@fast-check/packaged

npm i https://pkg.pr.new/@fast-check/packaged@6818

@fast-check/poisoning

npm i https://pkg.pr.new/@fast-check/poisoning@6818

@fast-check/vitest

npm i https://pkg.pr.new/@fast-check/vitest@6818

@fast-check/worker

npm i https://pkg.pr.new/@fast-check/worker@6818

commit: fa7ad21

Push the tag using refs/tags/ to explicitly push a tag (not a branch).
Draft releases don't create the tag on the remote, so --force is
unnecessary.

https://claude.ai/code/session_01NsbWgAUGTnBxikVhazo7hB
@dubzzz
dubzzz enabled auto-merge (squash) April 4, 2026 07:08
@dubzzz
dubzzz merged commit 501de9e into main Apr 4, 2026
49 checks passed
@dubzzz
dubzzz deleted the claude/push-tags-draft-releases-RoE4N branch April 4, 2026 07:12
@codecov

codecov Bot commented Apr 4, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.86%. Comparing base (e3875ed) to head (fa7ad21).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6818   +/-   ##
=======================================
  Coverage   94.86%   94.86%           
=======================================
  Files         209      209           
  Lines        5665     5665           
  Branches     1488     1488           
=======================================
  Hits         5374     5374           
  Misses        283      283           
  Partials        8        8           
Flag Coverage Δ
tests 94.86% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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.

2 participants