v7.0.0

v7.0.0

⚠️ Breaking Changes ⚠️

This new major release changes the way that "noop" style commands work. Starting with this release, the .deploy noop command will no longer work and it will be immediately replaced with .noop instead. The core reasoning for this, is so that .noop can become its own standalone command and no longer be a subset of the .deploy command. This will lead to less mistakes, user error, and higher flexibility when customizing this Action for future projects.

What do I need to do?

For most users, you don't need to do anything at all. Simply use .noop (the default) instead of .deploy noop. In fact, if you upgrade to v7.0.0 (this release) and run .deploy noop, you will be presented with a comment containing details about the command to use instead and a link to the deprecation docs

You can always customize the noop_trigger input option to be something else besides .noop (you could do .plan if you're doing Terraform things for example) but the "noop" trigger will never again be a subset of the primary deploy command.

Why was this change made?

Here are some suggested readings to learn more about why this change was made if you are curious to learn more:

• discussion issue
• pull request containing changes
• deprecation docs

What's Changed

• noop prefix enhancements by @GrantBirki in #169
• isDeprecated Function Fixes by @GrantBirki in #171
• node package updates by @GrantBirki in #172

Full Changelog: v6.1.0...v7.0.0