Skip to content

fix: harden v18 release workflow#8

Merged
SoonIter merged 1 commit into
v18from
fix/v18-release-dist-tag
May 22, 2026
Merged

fix: harden v18 release workflow#8
SoonIter merged 1 commit into
v18from
fix/v18-release-dist-tag

Conversation

@SoonIter
Copy link
Copy Markdown
Owner

@SoonIter SoonIter commented May 22, 2026

Summary

  • Set the v18 release workflow npm dist-tag to latest-v18.
  • Pin GitHub Actions in v18 workflows to commit hashes, matching the hardening style from chore(ci): harden github actions #4.
  • Move release permissions to the job scope and disable implicit setup-node package manager cache.

Testing

  • git diff --check
  • rg -n "uses: .*@v[0-9]" .github/workflows returns no matches

Copilot AI review requested due to automatic review settings May 22, 2026 06:42
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the npm publishing workflow to prevent React 18 (v18.x) releases of react-render-to-markdown from being published under npm’s default latest dist-tag when newer major versions (e.g., 19.x) exist.

Changes:

  • Set the npm publish dist-tag to latest-v18 in the release workflow.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/workflows/release.yml
@SoonIter SoonIter force-pushed the fix/v18-release-dist-tag branch from d22b7a7 to 10d3bb7 Compare May 22, 2026 06:46
@SoonIter SoonIter changed the title fix: publish v18 releases with latest-v18 dist tag fix: harden v18 release workflow May 22, 2026
@SoonIter SoonIter merged commit 20bc6b2 into v18 May 22, 2026
1 check 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.

2 participants