Bump Kir-Antipov/mc-publish from 3.1 to 3.3
Bumps Kir-Antipov/mc-publish from 3.1 to 3.3.
Release notes
Sourced from Kir-Antipov/mc-publish's releases.
mc-publish 3.3
⚠️ Pre-Release Warning ⚠️
Hello there, folks. Quick note that this is a pre-release. I was caught off guard by GitHub shifting their deprecation of Node.js 12 ahead of the originally stated Summer 2023 - turns out their idea of 'summer' is May 18th.
Should any issues arise, ping me on Discord at Kir_Antipov#4513, or open an issue on GitHub. I'm committed to promptly resolving critical problems (I'm pretty sure that there should be none, but still) as fast as possible and updating the release itself, so there's no extra work on your end.
I'm sorry for not delivering
v4.0as planned. This version might be a bit rougher around the edges than I would have liked, but it still brings great new features and bug fixes.Anyway, thank you for your patience and ongoing support!
Features:
- Node.js 16 compatibility introduced (#39)
- Full support added for game version ranges. Say goodbye to the
version-resolverworkaround. Use any range, like>=1.19 <1.19.3or even[3D Shareware v1.34,19w45b), and the action will interpret it as intended (#25)- A new
game-version-filterinput is now available- The
dependenciesinput now accommodates a more powerful, descriptive format- The warning message for unspecifying tokens has been made clearer (#40)
- Version types of unfeatured Modrinth versions are now recognized (#41)
- Consequently,
modrinth-unfeature-modehas been updated with three new flags (automatically incorporated into the existingsubset,intersection, andanypresets):
version-type-subsetversion-type-intersectionversion-type-any- The action now offers useful outputs (#54)
- CurseForge project ids can now be used as alternatives to slugs when specifying dependencies (#56)
Fixes:
- Older Modrinth versions will no longer be unfeatured if the new version's publication fails (#37)
- Actions will not fail when attempting to upload a plugin or resource pack to CurseForge (#42)
- The issue of
files-secondarybeing ignored has been resolved;files-secondaryis now deprecated and should not be used anymore. This counts as a fix, right? (#47)Obsolete Functionality:
This version initiates the migration away from legacy design decisions, aiming for complete deprecation by
v4.0. To be clear, your existing configurations should still operate as expected, so there's no immediate rush to update your configurations, especially if they are complex. At most, the action may emit a few deprecation warnings.
files-primaryandfiles-secondaryThis change is rather straightforward.
filesnow accepts an array of globs. (Honestly, I'm not sure why it wasn't like this from the start, as it seems much more logical). So, instead of:files-primary: primary-file*.jar files-secondary: secondary-files*.jarYou should now use:
files: | primary-file*.jar secondary-files*.jar </tr></table>
... (truncated)
Commits
1e27b36Buildcedc299Addedidvalidation to CurseForge and Modrinth uploaders1c5c51cidcan be read from metadata again77b76faFixed default value resolution inModrinthUploader3ee1a99Removed unnecessaryasync4dfe016Addedstripscripte5bcb4dAdded ability to remove custom fields from action metadata9f17eefGitHub does not allow custom entries inaction.ymla88dbf9Build5cb5700Fixed defaultGameVersionProviderresolution- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)