Upgrades & fixes

[LitoMore]

Current warning messages from our CI

The following actions uses node12 which is deprecated and will be forced to run on node16: LitoMore/simple-icons-release-action@b14cfca. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information, see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Changes

• Use Node.js 20 on CI
• Target this action runtime to Node.js 20
• Upgrade @actions/core to the latest to drop the deprecated API usages
• Upgrade @actions/github to the latest
• Remove unused stash commands from .husky/pre-commit
• Upgrade @zeit/ncc to @vercel/ncc (resolves Replace @zeit/ncc dependency by @vercel/ncc #72)
• Fix the package entry definition in pakcage.json
• Fix file.patch logic (Related to Release action fails simple-icons#8734 (comment))
• Allow triggering release by workflow dispatch
• Allow skipping release note with [skip] title prefix
• Allow skipping release note with skip release note label
• Add script fix-distribution-file for fixing @vercel/ncc's distribution
• Fix Jest tests
• Fix un-decoded HTML entities in the SVG title for release note
• Replace Generator with async/await

Also

• Fixes Update dependency semver to v7.5.2 [SECURITY] #75

Release plan

I'm going to create a new major release at this repository. And it's time to switch our action URL from my repo https://github.com/LitoMore/simple-icons-release-action to this one.

References

• https://jestjs.io/docs/ecmascript-modules

[adamrusted]

@LitoMore - does this bring this repo in line with your release action?

[LitoMore]

@adamrusted Yep. All changes are included.

The test part needs to be fixed. I'm checking.

[LitoMore]

@mondeja The test has been fixed. Please review.

[mondeja]

Thanks for this update @LitoMore 👍🏼

I suppose that it runs OK as haven't tested manually. The main problem of the regex not being able to detect some changes is not covered by the work here. So merging, in the future will fix that.