Add changeset tag to custom publishing section of README

[mholta]

Why is this pull request needed?

Based on #269.

What does this pull request change?

Add simple example of custom publishing workflow that produces GitHub Releases and Git tags.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9b099e6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[gtjamesa]

This PR definitely would have saved me reading through the source code

[helloint]

why is this not being merged?

[hirasso]

Is changesets still maintained?

[Andarist]

tbf - I think I have successfully used Changesets with custom release scripts like this:

      - name: Create Release Pull Request or Publish to npm
        id: changesets
        uses: changesets/action@v1
        with:
          publish: yarn run release

where the release script be defined like this:

    "release": "node ./scripts/release.js && yarn changeset tag"

This way you don't have to rely on steps.changesets.outputs.hasChangeset at all

[Andarist]

@hirasso it's maintained and I plan to spend more time on it in 2025 but it's an unpaid OSS work and my free time has limits 🤷‍♂️

[hirasso]

@Andarist sorry if my comment sounded too pushy! I'm an OSS maintainer myself so I should have known better 😇 ...and amazing to hear that changesets is still maintained! I'll leave my working solution here, I was only able to stitch together all required settings after reading through a few issues, PRs and the source code.

• I had defined the custom publish action but it was not doing anything (not even throwing a warning):

with:
  publish: pnpm changeset tag

• My package has "private": true in it's package.json
• I was missing {"privatePackages": { "version": true, "tag": true }} in my changeset .changeset/config.json and thus my package was being ignored:

https://github.com/changesets/changesets/blob/a3acd12146e888abb104a6a41399be8bba0f6169/packages/should-skip-package/src/index.ts#L18-L20

I think with a little more documentation setups like these would become much more straight forward.

Thank you for changesets, I love it ❤️