Skip to content

Add select-mode, version, pack and publish sub-actions#656

Open
bluwy wants to merge 9 commits into
mainfrom
new-version-publish-subaction
Open

Add select-mode, version, pack and publish sub-actions#656
bluwy wants to merge 9 commits into
mainfrom
new-version-publish-subaction

Conversation

@bluwy

@bluwy bluwy commented Jun 15, 2026

Copy link
Copy Markdown
Member

Adds a very simple implementation of /select-mode, /version, and /publish sub-actions that reuses functions from the root action. I renamed some of the inputs, copied most of the logic over. There's probably more cleanup possible but I don't want to stray too far for now.

I also did not write any readme/docs as I'm lazy maybe it changes after the publish-plan PRs.

I made this PR mainly so we can make updates on it easier later, but I'm also fine closing this as starting from scratch with the publish-plan stuff if that's easier.

@changeset-bot

changeset-bot Bot commented Jun 15, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: ae062ce

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

Comment thread version/action.yml Outdated
Comment thread version/action.yml Outdated
Comment thread src/version/index.ts Outdated
@Andarist Andarist force-pushed the new-version-publish-subaction branch from b6da0bd to 10ef577 Compare June 17, 2026 06:54
@Andarist Andarist changed the title Add select-mode, version, and publish sub-actions Add select-mode, version, pack and publish sub-actions Jun 20, 2026
Comment thread publish/action.yml
script:
description: "The command to use to publish packages"
required: false
packed-artifact-id:

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.

is this a good input name? maybe pack-dir-artifact-id would be better?

Comment thread src/run.ts
});
};

if (script) {

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.

Note how with a custom publish script we don't handle fromPackDir at all. My best idea to handle this would be to also add support for passing this argument~ through CLI args. That way the scripts could forward env to the underlying changesets publish kinda naturally - without messing with flags forwarding. Thoughts?

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