Skip to content

Add back cwd input - #718

Merged
bluwy merged 1 commit into
mainfrom
cwd-input-returns
Aug 12, 2026
Merged

Add back cwd input#718
bluwy merged 1 commit into
mainfrom
cwd-input-returns

Conversation

@bluwy

@bluwy bluwy commented Aug 12, 2026

Copy link
Copy Markdown
Member

close #717

@changeset-bot

changeset-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: d57c63b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@changesets/action Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@beeequeue

Copy link
Copy Markdown
Member

can we not just base it on working-directory (i.e. the CWD) rather than a duplicate option?

@Andarist

Copy link
Copy Markdown
Member

@beeequeue the issue mentions that working-directory directory doesn't work on steps using uses. This is... peculiar but well 🤷 And cwd input does sound better than a lengthy working-directory alternative

Comment thread pack/action.yml
description: "Artifact id for a publish plan generated by the select-mode subaction"
required: false
cwd:
description: "The working directory to execute Changesets in. Defaults to the root of the repository."

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Technically, it probably defaults to the current workspace dir or smth - but it's probably fine to assume the root of the repository here

@@ -0,0 +1,5 @@
---
"@changesets/action": minor

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

One could argue it should be a patch - im fine with either

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Yeah I'm also fine with either but I'll merge as minor for now, action versions are usually more lenient

@bluwy

bluwy commented Aug 12, 2026

Copy link
Copy Markdown
Member Author

And cwd input does sound better than a lengthy working-directory alternative

Yeah I was also thinking of re-using working-directory as the name, but it's probably easier for now to use the same name we had before.

@bluwy
bluwy added this pull request to the merge queue Aug 12, 2026
Merged via the queue into main with commit 3b7c71c Aug 12, 2026
7 checks passed
@bluwy
bluwy deleted the cwd-input-returns branch August 12, 2026 13:11
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.

[v2] Nested Changesets projects cannot be used: working-directory is invalid on uses steps

3 participants