mparticle / aquarium Goto Github PK

🚨 The automated release from the main 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 main 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 📦🚀

🚨 The automated release from the main 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 main 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.6.0 on branch main cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=1.5.0 <1.6.0 can be published from branch main.

The following commits are responsible for the invalid release:

• Fix: add check next to active workspace (#139) (786f7af)
• chore: stories (#107) (eb54749)
• feat: global navigation and styling (#124) (7863d9a)
• use latest node in release action (8b66a3a)
• Feat: global nav (#36) (591c3bb)
• Revert "build(deps-dev): bump ip from 2.0.0 to 2.0.1" (#116) (6a64805)
• build(deps-dev): bump ip from 2.0.0 to 2.0.1 (#115) (3781d1c)
• chore: global nav prep / cleanup (#105) (e740410)
• build: Applies vite default configs for bundling as a module and commonjs (#106) (996bfff)
• Chore: More stories (#86) (d56b26e)
• chore: Document linting and formatting decisions (#95) (9b2c61b)
• chore: tooltip stories (#89) (e24e2c9)
• update peer dependency versions (3b12208)
• Merge remote-tracking branch 'origin/main' (0dc53f9)
• create Pull Request Template (82f59d6)
• feat: Adds stylelint with recommended configs and rules from Indicative (#82) (4dd5380)
• Style: css tokens (#85) (8dcdd14)
• chore: Lock date of calendar story (cd33095)
• Merge pull request #66 from mParticle/feat/automated-formatting-and-linting (4cf6c21)
• package-lock update (f8d243e)
• Merge branch 'main' into feat/automated-formatting-and-linting (6146a21)
• package-lock update (165eae7)
• Merge branch 'main' into feat/automated-formatting-and-linting (76024ec)
• add expect import (4a547a7)
• Change checkableTag format (cadca52)
• Merge branch 'main' into feat/automated-formatting-and-linting (a563358)
• export Icon component again (a654790)
• Merge branch 'main' into feat/automated-formatting-and-linting (cf1d209)
• removes fragments from atom components (418962c)
• update package-lock (8a756e3)
• fix merge with main (4ddda0b)
• adds component list to explicit-function-return-type allowedNames (8aa713f)
• disables import/no-duplicates (b2108ae)
• configures allowNamedExports to be allowed on no-use-before-define rule (d1b72bd)
• Merge branch 'feat/automated-formatting-and-linting' of https://github.com/mParticle/aquarium into feat/automated-formatting-and-linting (f3d6c6d)
• prettier 120 printWidth (a869150)
• Update src/components/feedback/LoadingModal/LoadingModal.tsx (d959a13)
• disables @typescript-eslint/consistent-type-definitions (6247d54)
• fix reviews (293ba07)
• format storybook config files (de807e3)
• revert prettier printWidth (e074c8c)
• update package-lock (902a220)
• Fixes reviews from #3 (9a71223)
• fixes eslint stuff (5efb11d)
• fix reviews from #62 (cc91704)
• fix all eslint problems (9a30d24)
• Now able to close AnnotationModal on story (8fdc4db)
• Automatic fixes from eslint (1f64fe2)
• prettier --write for the first time (66a202f)
• Testing pre-commit hook (19daf47)
• Initial prettier and eslint configuration (e847659)
• fix merge (a11feee)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch main 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 📦🚀