Giter Club home page Giter Club logo

workspace's Introduction

Work playspace

This project was generated using Nx.

workspace's People

Contributors

guiseek avatar semantic-release-bot avatar

Stargazers

Helton avatar

Watchers

James Cloos avatar avatar avatar

workspace's Issues

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

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

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 resolve 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 is 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.1.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.0.1 <1.0.2 can be published from branch main.

The following commits are responsible for the invalid release:

  • chore(card): release 1.2.0 (7de5189)
  • feat(card): desafios e comunidades (3b2d40d)
  • chore(hacktoberfest-br): release 1.0.0 (fa78d48)
  • feat(hacktoberfest-br): invite (c026346)
  • feat(paper): enter-password component (fd948c2)
  • feat(chat-data): added data library for chat grouped directory (869918f)
  • feat(chat-client): added client for realtime library (4c8f908)
  • feat(chat-server): added server for realtime library (c3cc723)
  • Forms (#7) (2caa0ef)

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 📦🚀

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

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

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 resolve 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 is 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.1.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.0.1 <1.0.2 can be published from branch main.

The following commits are responsible for the invalid release:

  • chore(card): release 1.2.1 (fd15197)
  • fix(card): labels - pt-br to en-US (#14) (e47f443)
  • ci(misc): ci insert version (ece64d5)
  • chore(card): release 1.2.0 (7de5189)
  • feat(card): desafios e comunidades (3b2d40d)
  • chore(hacktoberfest-br): release 1.0.0 (fa78d48)
  • feat(hacktoberfest-br): invite (c026346)
  • feat(paper): enter-password component (fd948c2)
  • feat(chat-data): added data library for chat grouped directory (869918f)
  • feat(chat-client): added client for realtime library (4c8f908)
  • feat(chat-server): added server for realtime library (c3cc723)
  • Forms (#7) (2caa0ef)

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 📦🚀

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

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

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 resolve 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 is 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.1.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.0.1 <1.0.2 can be published from branch main.

The following commits are responsible for the invalid release:

  • feat(paper): enter-password component (fd948c2)
  • feat(chat-data): added data library for chat grouped directory (869918f)
  • feat(chat-client): added client for realtime library (4c8f908)
  • feat(chat-server): added server for realtime library (c3cc723)
  • Forms (#7) (2caa0ef)

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 📦🚀

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.