🦋 Changeset release

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

lint-staged@15.0.0

Major Changes

• #1322 66b93aa Thanks @iiroj! - Require at least Node.js 18.12.0

  This release drops support for Node.js 16, which is EOL after 2023-09-11.
  Please upgrade your Node.js to the latest version.

  Additionally, all dependencies have been updated to their latest versions.

[iiroj]

Woohoo, finally got this far @okonet !

[iiroj]

I wonder why this PR is not triggering the usual actions.

[iiroj]

@okonet what do you think, should we just remove the "required/expected checks"? IMO as long a PR cannot be merged without an approval, and all checks are passing, it should be fine...

[iiroj]

This indicates that when using the GITHUB_TOKEN, it won't trigger a new workflow: https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow

[okonet]

I’d rather keep the checks and use administrative rights to merge for these kind of PRs

[okonet]

Feel free to merge if you’re happy with it.

[iiroj]

Alternatively we could set up a PAT instead of using the default GITHUB_TOKEN. I will also google around if there's other ways.

[iiroj]

I guess just using the admin powers to merge is fine. I'll create a new small PR just to make sure this changeset PR gets automatically updated correctly.

[iiroj]

@okonet feel free to merge this, I don't have permissions because of the required checks.

[okonet]

You should be able now. Let me know…

[iiroj]

Unfortunately, we need to set up a Personal Access Token for running the Actions, since now the tag workflow didn't trigger. Can you publish 15.0.0 manually to npm? I'll open a PR for the PAT change.

[iiroj]

On second thought, I will try to re-create the v15.0.0 git tag to trigger the Action.

[iiroj]

I was able to make it work by adjusting the CI config a bit, and creating the Personal Access Token. Unfortunately, I have a npm script collision with the name publish... have to change that.

EDIT: PR here #1336