Fix to release scripts when called in other repos#65
Merged
Conversation
…work when used in other repos
amcclain
approved these changes
Apr 7, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Replaced $GITHUB_WORKSPACE paths with $GITHUB_ACTION_PATH so actions work when used in other repos.
This bug broke the release scripts when called from other repos; it just so happened that only the release scripts used the GITHUB_WORKSPACE variable, the snapshot scripts did not.
Fix to the error encountered here when trying to release hoist-react using the new code:
Using the GITHUB_WORKSPACE address accessed the local directory in hosit-react, which lacks the scripts present in hoist-dev-utils. This to have an easy remedy - use the GITHUB_ACTION_PATH instead.
According to https://docs.github.com/en/actions/reference/workflows-and-actions/variables
$GITHUB_WORKSPACE is "The default working directory on the runner for steps, and the default location of your repository when using the checkout action."
$GITHUB_ACTION_PATH is "The path where an action is located. This property is only supported in composite actions. You can use this path to change directories to where the action is located and access other files in that same repository. For example, /home/runner/work/_actions/repo-owner/name-of-action-repo/v1."
These two actions are already "composite" actions for this very reason, it appears we were simply using the wrong variable in these two spots.