Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency next-translate to v1.4.0 #14

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 27, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
next-translate 1.0.7 -> 1.4.0 age adoption passing confidence

Release Notes

vinissimus/next-translate

v1.4.0

Compare Source

We reintroduce this feature by @​ajmnz and @​gurkerl83 , that it was once added by #​574, but got removed because of #​604.

Also added loggerEnvironment in configuration in https://github.com/vinissimus/next-translate/pull/683 by @​edwinveldhuizen

What's Changed

New Contributors

Full Changelog: aralroca/next-translate@1.3.5...1.4.0

v1.3.5

Compare Source

What's Changed

New Contributors

Full Changelog: aralroca/next-translate@1.3.4...1.3.5

v1.3.4

Compare Source

What's Changed

New Contributors

Full Changelog: aralroca/next-translate@1.3.3...1.3.4

v1.3.3

Compare Source

1.3.2 instead of solve the problem add another one. So in 1.3.3 I revert the commit from 1.3.2 and reopen the issue to solve it with a different approach.

Issue from 1.3.2: https://github.com/vinissimus/next-translate/issues/769

Changes

  • Revert "Fix conflicts with comments on webpack loader (#​768)" bbaa3bf

Full Changelog: aralroca/next-translate@1.3.2...1.3.3

v1.3.2

Compare Source

1.3.1 is broken and replaced to 1.3.2:

What's Changed

Full Changelog: aralroca/next-translate@1.3.0...1.3.2

v1.3.1

Compare Source

v1.3.0

Compare Source

What's Changed

New Contributors

Full Changelog: aralroca/next-translate@1.2.0...1.3.0

v1.2.0

Compare Source

PATCHES

FEATURES

v1.1.1

Compare Source

v1.1.0

Compare Source

New release with a new feature thanks to @​tomvardasca, and with an important fix for monorepos like Nx. Also for those who use a custom server can change the locale from Node with req.locale.


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@vercel
Copy link

vercel bot commented Oct 27, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/yadgithub/zulybot/6Zb4PT4WG8Mpz9RYZ5kqcdaPZhYd
✅ Preview: https://zulybot-git-renovate-next-translate-1x-yadgithub.vercel.app

@renovate renovate bot changed the title Update dependency next-translate to v1.1.1 Update dependency next-translate to v1.2.0 Nov 7, 2021
@renovate renovate bot force-pushed the renovate/next-translate-1.x branch from f684a5b to 1c82b31 Compare November 7, 2021 16:28
@renovate renovate bot force-pushed the renovate/next-translate-1.x branch from 1c82b31 to 255b53d Compare March 7, 2022 08:35
@renovate renovate bot changed the title Update dependency next-translate to v1.2.0 Update dependency next-translate to v1.3.5 Mar 7, 2022
@renovate renovate bot changed the title Update dependency next-translate to v1.3.5 Update dependency next-translate to v1.4.0 Apr 24, 2022
@renovate renovate bot force-pushed the renovate/next-translate-1.x branch from 255b53d to 88502bd Compare April 24, 2022 21:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant