buddywinangun-bot[bot]
commented
7 months ago :rotating_light: The automated release from the master branch failed. :rotating_light:
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:
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.0.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.0.0 <1.0.0 can be published from branch master.
The following commits are responsible for the invalid release:
- ci: release (0cbb0a6)
- chore: changelog.md (64ad4a8)
- fix: repository property (2ccf94f)
- fix: files name (0a74e9d)
- refactor: code base (0a1a7d3)
- perf: upgrade repo to monorepo (0270a3b)
- changelog (c155026)
- changelog (9434660)
- added: depenencies twing (d82b99e)
- changed: twig args (351b28a)
- changed action release drafter (6000bba)
- upgrade mayor release (c263d5b)
- remove: strip-indent (3723543)
- fixed: template tasks (9ce2f7e)
- removed: require-dir node_modules (9dba0ee)
- Added: release-drafter.yml (28055ba)
- Create jekyll-gh-pages.yml (2881207)
- Update release-notes.yml (552a337)
- changed: banner locations (4ec271b)
- fixed: script taks (06a0179)
- changed: version (90ab527)
- added: static-tasks (05c327f)
- changed: bin.js (d1c1233)
- changed: readme.md (03abad5)
- changed: postinstall-script (7fa2352)
- changed: workflow (80a0b89)
- changed: folder assets (82341b1)
- changed: start package.json (48686f6)
- changed: version (d878856)
- Merge branch 'master' into v3.x (5181de0)
- added: extract task (32afe6c)
- Merge branch 'master' into v3.x (6c41b33)
- fixed: post install script (2841ccc)
- changed: workflow (3bf03d1)
- Delete .github/workflows/release-package.yml (018bc49)
- Create npm-publish-github-packages.yml (9a9e2e5)
- chenged: workflows (f567d4e)
- Merge remote-tracking branch 'origin/master' into v3.x (6ed2fba)
- changed: version (b766bcb)
- changed: changelog.md (b28a4f2)
- added: workflow (b76bc85)
- added: path (75ef1a5)
- changed: scripts (977f036)
- changed: readme.md (f416abc)
- added: readme.md in start themes (8c57f58)
- added: test folder (803ba79)
- remove: projects folder (a49ee00)
- changed: helper to lib folder (2428f21)
- changed: config.js (c7d84fe)
- change: chnagelog.md (2126a0c)
- changed: normalisasi tasks (c27d342)
- changed: style task to sass task (52ace12)
- changed: readme.md (639a1b6)
- changed: .gitignore (27aab05)
- added: comment (63bc231)
- changed: template task (060ea1c)
- changed: config.js for each project (9d77e7f)
- changed: package.json for each project (df0f5fc)
- added: svg task (2052a21)
- added: bundle vendor task on template task (5f879ac)
- changed: template task (bffb2c3)
- changed: readme.md (e7006ba)
- added: script task (deface6)
- changed: readme.md (18d4fc1)
- added: style task (10eb358)
- changed: readme.md (fd1e060)
- added: static task (d5ffef8)
- changed: readme.md (c3ebbfb)
- added: template task (ff20d82)
- fixed: gulp msg version (6fb168b)
- fixed: export config (d30e0b2)
- changed: readme.md (43eab3a)
- added: create task (084b6e9)
- added: gulpfile.js (664b3cc)
- added: folder project (13b1d3c)
- added: package.json (a0b3136)
- initial commit (3070404)
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 :package::rocket:
:rotating_light: The automated release from the
masterbranch failed. :rotating_light: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
masterbranch. 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:
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.0.0on branchmastercannot be published as it is out of range.Based on the releases published on other branches, only versions within the range
>=1.0.0 <1.0.0can be published from branchmaster.The following commits are responsible for the invalid release:
Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch
masterwith 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 :package::rocket: