Orfium/orfium-ictinus

The automated release is failing 🚨

Closed this issue · 0 comments

github-actions commented

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

Based on the releases published on other branches, only versions within the range >=3.9.3 can be published from branch next.

The following commits are responsible for the invalid release:

  • Merge pull request #375 from Orfium/chore/merge-master-v4 (6797c49)
  • Merging master branch to next (45677e6)
  • Merge pull request #371 from Orfium/chore/upgrade-ci-node (01e516f)
  • chore: update ci to node 14.17 (b968b5a)
  • Merge pull request #343 from Orfium/feat/new-color-generator (eb9c616)
  • chore: update from PR comments (5a3a356)
  • chore: add comment for complicated code (c1152af)
  • chore: update colors per design request on specific component, add list on breadcrumb (8a8df10)
  • chore(button): update how transparent calculates with fix on link (e6e32a6)
  • chore: update all PR review comments (8e87b28)
  • chore: update assetMatching iterations on utils from one to two (43a8424)
  • chore: use flat pallete colors when using theme provider on preview (b206039)
  • style(table): update border color, hover and select based on QA (633dcb5)
  • style(calendar): update all color mapping to new colors from new palette (5de44e2)
  • feat(colors): add new pale palette and add support to get color function for it (3827fc5)
  • style(AssetMatch): update styling of asset match based on QA (366de80)
  • style(elevation): update elevation with new per QA (09b6177)
  • style(filter): fix swatches coloring issue after color update (1b8fe1c)
  • style(notification): update all actions with button new type link, apply new inline notif style per QA (ffbda88)
  • style(topAppBar): update dark mode colors and avatar sizes for the specific case (6e3d58a)
  • style(drawer): fix paddings and color of drawer per design QA (cf0f26a)
  • style(tooltip): update tooltip default background based on design QA (04bde66)
  • style(button): update padding of large button (ab8b926)
  • style(radio): update select colors based on the design QA (0436613)
  • style(select): update select colors based on the design QA (184601e)
  • chore: rename lightTintedGrey to lightGrey (214646e)
  • feat(palette): fix new black color for swatches (14150b0)
  • chore: add primary and secondary to ictinus according to figma (9a8120c)
  • fix(palette): base shade to pick the correct color (b322631)
  • fix(palette): test for async search after replacing wrong values (e850576)
  • Merge branch 'master' into feat/new-color-generator (ca35ae4)
  • feat(palette): update storyshots with new colors and documentation about new namings (87e2728)
  • fix(palette): remove unused console.log (2ea0c00)
  • doc(palette): change all documention ref to old base from 400 -> 500 (34e4560)
  • feat(palette): new color palette colors, palette calculations and replacements for all (450c3b6)
  • feat(palette): new generator test (50c1c53)

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

A valid branch could be master or next.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀