The automated release is failing 🚨 about firebolt-apis HOT 1 CLOSED

🚨 The automated release from the refactor/one-repository 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 refactor/one-repository 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 0.9.0 on branch refactor/one-repository cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=0.10.0 can be published from branch refactor/one-repository.

The following commits are responsible for the invalid release:

• chore: Tag for ... (#76) (a0ad96f)
• chore(release): Changing test to beta (5c4e16d)
• chore(release): Pointing to workspace releaserc (6f326c5)
• chore(release): Remove github releases from workspaces (11915e0)
• chore(release): Adding tokens (e433b59)
• chore(release): Testing out semantic-release (17f4037)
• chore(ci): Update CI YAML (06ae314)
• fix: Word publish scripts (#78) (4d76142)
• chore: Tag for ... (#76) (a51952c)
• chore: Turn off dry run (b84bf33)
• feat: Turn on dryRun (0e44d4e)
• feat: Trigger (90248d2)
• feat: Trigger (0e9ae6f)
• feat: Trigger (991cfd3)
• chore: Remove next-major from releaserc (2573aac)
• feat: Trigger (ec41f09)
• feat: Trigger (c73e042)
• feat: Trigger (296fc5a)
• feat: Trigger (157050c)
• chore: Turn off dryRun (54c0504)
• feat: Trigger (763bbd1)
• feat: Turn on dryRun (1b858dc)
• fix: Updated secure storage spec to allow null as result value (#84) (d123ff5)
• fix: Change doc examples to https (#79) (68f7757)
• fix: FIRESDK-31 returned response from Lifecycle.ready method (#81) (4d80ba2)
• fix: Word publish scripts (#78) (9f25f63)
• feat: Add Secure Storage module (#77) (e932aaa)
• chore: Tag for ... (#76) (2a47d14)
• chore: Tag for ... (#75) (4397355)
• ci: Release to npm and github on merge to next (#67) (6c3ae69)
• ci: Do publish to npm using a branch-based dist-tag [skip ci] (9548fd6)
• fix: Don't ignore source files when pulbishing to npm [skip ci] (2fa4c9f)
• chore: Update .releaserc [skip ci] (dfbcd41)
• chore: Update release-github.yml [skip ci] (3a865f1)
• chore: Update typo [skip ci] (1e90bf3)
• ci: Update .releaserc (3bb0338)
• ci: Publish tarball in github release (ff15d88)
• fix: Build SDK before npm publish (#64) (b28e639)
• chore: manual changelog edits (#62) (ac1a551)
• ci(commitlint): Allow Caps, and also, punctuation! (#56) (ee0727a)
• docs: fix typo in device version (d04e8da)
• ci: changes to release automation (#61) (47175a0)
• chore(oops): removing accidentally committed dist files (4050d00)
• Update CHANGELOG.md (a151276)
• chore(release): 0.9.0-next.1 [skip ci] (0e591aa)
• ci: update release assets (#60) (b42b2d6)
• chore(release): 0.9.0-next.1 [skip ci] (0c6b87f)
• feat(extensions): extensions module (7cf4128)
• fix(device): add device version firmware property (ef12ec0)
• chore(release): 0.8.1-next.1 [skip ci] (6da2aea)
• fix(lifecycle): lifecycle state api returns correct state in all circumstances (31e405c)
• ci: release automation on next branch (#52) (5d25617)
• adding typescript files (#41) (c5f7f4e)

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

A valid branch could be main or refactor/one-repository.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

from firebolt-apis.