Skip to content

fix: use payload.release.tag_name for npm package release #1665

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

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

JoshuaKGoldberg
Copy link
Owner

PR Checklist

Overview

Uses ${{ payload.release.tag_name }} this time, as suggested.

💖

@JoshuaKGoldberg JoshuaKGoldberg merged commit 96bf717 into main Oct 17, 2024
15 checks passed
@JoshuaKGoldberg JoshuaKGoldberg deleted the payload-release-tag-name branch October 17, 2024 23:58
JoshuaKGoldberg added a commit that referenced this pull request Oct 18, 2024
## PR Checklist

- [x] Addresses an existing open issue: fixes broken post-release after
#1663 and #1665
- [x] That issue was marked as [`status: accepting
prs`](https://github.com/JoshuaKGoldberg/create-typescript-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22status%3A+accepting+prs%22)
- [x] Steps in
[CONTRIBUTING.md](https://github.com/JoshuaKGoldberg/create-typescript-app/blob/main/.github/CONTRIBUTING.md)
were taken

## Overview

Sigh.

💖
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.

🛠 Tooling: Investigate simplifying release commenter version name
1 participant