fix(ci): create-an-issue in release workflow is pinned to incorrect hash
#12004
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zerosnacks
requested review from
0xrusowsky,
DaniPopes,
grandizzy,
mattsse,
onbjerg and
yash-atreya
as code owners
zerosnacks
changed the title
ci): ci): create-an-issue in release workflow is pinned to incorrect hash
grandizzy
approved these changes
Oct 7, 2025
onbjerg
approved these changes
Oct 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Current
releaseworkflow does not correctly open an issue, this is becausecreate-an-issuewas pinned to the latest commit onmainwhich does not include thedistdirectory. Instead it should refer to a commit made on a release tag that does: https://github.com/JasonEtco/create-an-issue/releases/tag/v2.9.2Solution
Original commit does not include dist directory, tag commit does: JasonEtco/create-an-issue@1b14a70, pinned it to that commit
It may be possible that Dependabot falsely will prompt for an update, if that is the case we can consider pinning this to the tag
v2.9.2insteadPR Checklist