Skip to content

feat(release-notes): dry-run#20

Closed
adrmachado-public wants to merge 2 commits into
mainfrom
/feat/dry-run-typescript
Closed

feat(release-notes): dry-run#20
adrmachado-public wants to merge 2 commits into
mainfrom
/feat/dry-run-typescript

Conversation

@adrmachado-public

Copy link
Copy Markdown
Contributor

Two fixes to actions/release-notes/action.yml:

  • add explicit actions/setup-node@v6 step — the action previously assumed Node.js was already set up by a prior action in the same job, creating a fragile implicit dependency
  • Replace awk/heredoc with TypeScript — the CHANGELOG parsing step used a multi-line awk expression writing to GITHUB_OUTPUT. Replaced with node dist/extract-release-notes.js (from the feat/git-utils PR)
  • add dry-run boolean input to release-pipeline, and thread it to version-bump, npm-publish, and release-notes

tweaks:

  • update the stale-branches action and pin to the latest commit SHA

@adrmachado-public
adrmachado-public marked this pull request as ready for review June 5, 2026 20:48

@GoogilyBoogily GoogilyBoogily left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

One small thing, and it's a my b

Comment on lines +21 to +24
- name: "Setup Node.js"
uses: actions/setup-node@v6
with:
node-version-file: .nvmrc

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I know this was a me thing, but we should swap to use our own custom setup-node action

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

this was missed in a lot of files, so the pr has gotten a lil thicker

@adrmachado-public

Copy link
Copy Markdown
Contributor Author

ok genuinely no idea what happened but when i tried to use jujutsu to move the bookmark forward it?? removed the forward slash??? i opened up a new PR #21 instead

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