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

chore(deps): update dependency next-intl to v2.19.1 - autoclosed #479

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 4, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
next-intl (source) 2.17.0 -> 2.19.1 age adoption passing confidence

Release Notes

amannn/next-intl (next-intl)

v2.19.1

Compare Source

Bug Fixes
  • Handle case where the locale param is an array and set cookie expiration to one year (#​435) (82e842c)

v2.19.0

Compare Source

Features

v2.18.0

Compare Source

Features

2.17.5 (2023-07-07)

Bug Fixes
  • Use ESM build only for browser bundlers (not Node.js) (#​386) (34a69f2)

2.17.4 (2023-07-05)

Bug Fixes

2.17.3 (2023-07-05)

Bug Fixes
  • Forward optional remaining args from Next.js router to wrapped useRouter (3ff878c)

2.17.2 (2023-07-05)

Bug Fixes

2.17.1 (2023-07-04)

Bug Fixes
  • Switch to tsup for more efficient bundling and also switch to vitest internally (#​375) (bf31626)

v2.17.5

Compare Source

Bug Fixes
  • Use ESM build only for browser bundlers (not Node.js) (#​386) (34a69f2)

v2.17.4

Compare Source

Bug Fixes

v2.17.3

Compare Source

Bug Fixes
  • Forward optional remaining args from Next.js router to wrapped useRouter (3ff878c)

v2.17.2

Compare Source

Bug Fixes

v2.17.1

Compare Source

Bug Fixes
  • Switch to tsup for more efficient bundling and also switch to vitest internally (#​375) (bf31626)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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, check this box

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

@renovate renovate bot requested a review from sullivanpj as a code owner July 4, 2023 14:42
@vercel
Copy link

vercel bot commented Jul 4, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
open-system ❌ Failed (Inspect) Aug 1, 2023 11:47am

@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from 108f944 to 107a5fc Compare July 5, 2023 03:11
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from 107a5fc to 0082c4d Compare July 5, 2023 04:02
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from 0082c4d to 8267ca8 Compare July 5, 2023 07:38
@renovate renovate bot changed the title chore(deps): update dependency next-intl to v2.17.1 chore(deps): update dependency next-intl to v2.17.2 Jul 5, 2023
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from 8267ca8 to 6a58944 Compare July 5, 2023 12:17
@renovate renovate bot changed the title chore(deps): update dependency next-intl to v2.17.2 chore(deps): update dependency next-intl to v2.17.3 Jul 5, 2023
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from 6a58944 to 6c1bf90 Compare July 5, 2023 15:26
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from 6c1bf90 to ce0fdeb Compare July 5, 2023 20:08
@renovate renovate bot changed the title chore(deps): update dependency next-intl to v2.17.3 chore(deps): update dependency next-intl to v2.17.4 Jul 5, 2023
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch 2 times, most recently from c660e23 to b1710c8 Compare July 7, 2023 01:32
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from b1710c8 to 492222c Compare July 7, 2023 01:57
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from 492222c to e264f82 Compare July 7, 2023 03:41
@renovate renovate bot changed the title chore(deps): update dependency next-intl to v2.17.4 chore(deps): update dependency next-intl to v2.17.5 Jul 7, 2023
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from e264f82 to e27db6a Compare July 7, 2023 10:04
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from e27db6a to 0316a28 Compare July 7, 2023 22:54
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from 0316a28 to f21fa46 Compare July 8, 2023 01:37
@renovate renovate bot changed the title chore(deps): update dependency next-intl to v2.17.5 chore(deps): update dependency next-intl to v2.19.0 Jul 24, 2023
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from f21fa46 to b17c97e Compare July 24, 2023 14:08
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from b17c97e to 4e79530 Compare July 29, 2023 03:31
@renovate renovate bot changed the title chore(deps): update dependency next-intl to v2.19.0 chore(deps): update dependency next-intl to v2.19.1 Aug 1, 2023
@renovate renovate bot force-pushed the renovate/next-intl-2.x-lockfile branch from 4e79530 to 5873d9b Compare August 1, 2023 11:46
@renovate renovate bot changed the title chore(deps): update dependency next-intl to v2.19.1 chore(deps): update dependency next-intl to v2.19.1 - autoclosed Aug 2, 2023
@renovate renovate bot closed this Aug 2, 2023
@renovate renovate bot deleted the renovate/next-intl-2.x-lockfile branch August 2, 2023 09:53
@github-actions github-actions bot locked and limited conversation to collaborators Aug 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants