If we could write a codemod for migrating i18next projects to lingui with one command, probably old projects with i18next will think to move to Lingui 👍🏻

For my side, I don't have so much experience with i18next, so give me some weeks to analyze how does it works to write the required mods for lingui :)

Mods

• ,,,

Are there plans for a V3 --> V4 codemod? The major breaking change I see is that the effective meaning of t has changed, so that where it used to just do the translation, now it gives you a hash. If I understand correctly, we need to add const { i18n } = useLingui(); and replace

t`hello`

with

i18n._(msg(`hello`))

(ref). But perhaps that last step is just a regex search replace, and there's no need for a codemod?

🚨 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:

• 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.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

How does it works?

semantic-release package contains all the necessary actions to:

• @semantic-release/commit-analyzer: Will analyze all the commits since the latest tagged release and will detect what version needs to be increased to match the commits spec.
  For example of commits and his response:

  • fix(): commit : x.x.1 - Patch

  • feat(): commit : x.1.x - Feature

  • `perf(pencil): remove graphiteWidth option

    BREAKING CHANGE: The graphiteWidth option has been removed.
    The default graphite width of 10mm is always used for performance reasons.
    ` : 1.x.x - Breaking change

• @semantic-release/release-notes-generator: Generate release notes for the commits added since the last release with conventional-changelog

• @semantic-release/changelog: Create or update the changelog file in the local project repository

• @semantic-release/npm: Publish the package on the npm registry

• @semantic-release/git: Push a release commit and tag, including configurable files

• @semantic-release/github: Publish a GitHub release

What's the best strategy?

All the pull requests merged should be merged following the conventional-commits standard in that way we'll create a history since the latest release. (if some user is not following the standard is a best practice to squash merge to overwrite the pull request history, and add a new commit name)

So when we're ready to deploy our version we just have to move up to Github Actions tab and deploy manually the version.

What happens once we triggered that manual action?

yarn release will be executed and of course all the above steps mentioned.

Will publish to npm the package, create a CHANGELOG.md, update the package.json version, create a git tag, and a commit with all the changes since the latest release (changelog, package.json..)

If some user has specified that some commit fixes any issue and in the commit appears the id of the issue, automatically semantic-release-bot will close that issue 🆒

Examples

I use this strategy on big libraries like http://github.com/rematch/rematch/, and other tiny libraries like https://github.com/semoal/themeprovider-storybook, and for me fits perfectly =)

Pending tasks

• Create a secret on project settings with a valid npm token to publish to npm. (I can't do it by permissions, can't access to project settings)

    NPM_TOKEN: ${{ secrets.NPM_TOKEN }}