nitzano / semantic-release-github-milestones Goto Github PK

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

• Add octokit/rest
• Add mock functions: listMilestones, getMilestoneByName,

Run tests for merge requests and master

• Find the milestone in verify-release stage
• Search by version name, branch, or channel

Hi!
I'd like to try out this plugin, but it fails to execute.
What can I do about this?

+ semantic-release
[11:11:19 AM] [semantic-release] › ℹ  Running semantic-release version 19.0.5
[11:11:19 AM] [semantic-release] › ✖  An error occurred while running semantic-release: Error [ERR_REQUIRE_ESM]: require() of ES Module /usr/local/lib/node_modules/semantic-release-github-milestones/node_modules/aggregate-error/index.js from /usr/local/lib/node_modules/semantic-release-github-milestones/build/verify-conditions/verify-github.js not supported.
Instead change the require of index.js in /usr/local/lib/node_modules/semantic-release-github-milestones/build/verify-conditions/verify-github.js to a dynamic import() which is available in all CommonJS modules.
    at Object.<anonymous> (/usr/local/lib/node_modules/semantic-release-github-milestones/build/verify-conditions/verify-github.js:44:41)
    at Object.<anonymous> (/usr/local/lib/node_modules/semantic-release-github-milestones/build/index.js:40:23)
    at loadPlugin (/usr/local/lib/node_modules/semantic-release/lib/plugins/utils.js:51:36)
    at /usr/local/lib/node_modules/semantic-release/lib/plugins/index.js:17:37
    at Array.reduce (<anonymous>)
    at module.exports (/usr/local/lib/node_modules/semantic-release/lib/plugins/index.js:14:34)
    at module.exports (/usr/local/lib/node_modules/semantic-release/lib/get-config.js:84:35)
    at async module.exports (/usr/local/lib/node_modules/semantic-release/index.js:265:32)
    at async module.exports (/usr/local/lib/node_modules/semantic-release/cli.js:55:5) {
  code: 'ERR_REQUIRE_ESM'
}
Error [ERR_REQUIRE_ESM]: require() of ES Module /usr/local/lib/node_modules/semantic-release-github-milestones/node_modules/aggregate-error/index.js from /usr/local/lib/node_modules/semantic-release-github-milestones/build/verify-conditions/verify-github.js not supported.
Instead change the require of index.js in /usr/local/lib/node_modules/semantic-release-github-milestones/build/verify-conditions/verify-github.js to a dynamic import() which is available in all CommonJS modules.
    at Object.<anonymous> (/usr/local/lib/node_modules/�[4msemantic-release-github-milestones�[24m/build/verify-conditions/verify-github.js:44:41)
    at Object.<anonymous> (/usr/local/lib/node_modules/�[4msemantic-release-github-milestones�[24m/build/index.js:40:23)
    at loadPlugin (/usr/local/lib/node_modules/�[4msemantic-release�[24m/lib/plugins/utils.js:51:36)
    at /usr/local/lib/node_modules/�[4msemantic-release�[24m/lib/plugins/index.js:17:37
    at Array.reduce (<anonymous>)
    at module.exports (/usr/local/lib/node_modules/�[4msemantic-release�[24m/lib/plugins/index.js:14:34)
    at module.exports (/usr/local/lib/node_modules/�[4msemantic-release�[24m/lib/get-config.js:84:35)
    at async module.exports (/usr/local/lib/node_modules/�[4msemantic-release�[24m/index.js:265:32)
    at async module.exports (/usr/local/lib/node_modules/�[4msemantic-release�[24m/cli.js:55:5) {
  code: �[32m'ERR_REQUIRE_ESM'�[39m
}

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The release 1.3.0 on branch master cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.2.1 <1.2.2 can be published from branch master.

The following commits are responsible for the invalid release:

• feat: display milesteons information while publishing (#23) (ee02e9d)
• 16 show release banner (#21) (b79bea0)
• Merge pull request #20 from nitzano/next (7121da6)
• test111 (fc7ebe3)
• chore: update lock (8d49cb5)
• Merge branch 'next' of github.com:nitzano/semantic-release-github-milestones into next (9c0e12f)
• fix (2160b6c)
• push repo name and owner inside (e809106)
• temp fix (44c43e0)
• added semantic release error (8be6349)
• show repo url (38d6417)
• added git parser (509523b)
• test before releasing (31f0398)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch master with git revert or git reset.

A valid branch could be next.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Add an option verifyMilestones (default false) to prevent releasing when there are open issues on the milestone

Since new semantic release is now ESM - migrate the plugin to be ES Module as well

When running semantic release, in the verifyRelease stage, display with a banner how many open milestones exist which match the name

Add dependabot support to add updates to next channel

When searching for milestones return only opened ones

Make milestones be case insensitive when turning on caseSensitive: false (default true)

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The release 1.3.0 on branch master cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.2.1 <1.2.2 can be published from branch master.

The following commits are responsible for the invalid release:

• chore(ci): start publishing on beta (5f6c5aa)
• feat: display milesteons information while publishing (#23) (ee02e9d)
• 16 show release banner (#21) (b79bea0)
• Merge pull request #20 from nitzano/next (7121da6)
• test111 (fc7ebe3)
• chore: update lock (8d49cb5)
• Merge branch 'next' of github.com:nitzano/semantic-release-github-milestones into next (9c0e12f)
• fix (2160b6c)
• push repo name and owner inside (e809106)
• temp fix (44c43e0)
• added semantic release error (8be6349)
• show repo url (38d6417)
• added git parser (509523b)
• test before releasing (31f0398)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch master with git revert or git reset.

A valid branch could be next.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Add support to semantic-release 22.0

• Allow to list miestones in src/github/get-milestones.ts

Add a banner to the release note at the end/begining of it:

"This version closed X issues in Y milestones`

When releasing a version which matches a milestone, append it's link to the release notes:

For example:

### Milestones
* [v1.1.4](LINK)

Allow to close the milestone after releasing the branch/version

• Add typescript
• Add xo
• Add husky + lint-staged
• Lint on push