Update dependency gatsby-link to v4.25.0

Open renovate[bot] opened this issue 3 years ago • 1 comments

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
gatsby-link (source)	`4.17.0` -> `4.25.0`

Release Notes

gatsbyjs/gatsby (gatsby-link)

`v4.25.0`

Compare Source

`v4.24.1`

Compare Source

Note: Version bump only for package gatsby-link

`v4.24.0`

Compare Source

🧾 Release notes

Bug Fixes

Correct handling of trailingSlash & pathPrefix fix #36542 (85b1319)

Chores

allow react/react-dom@experimental #36533 (7ef4a3f)

`v4.23.0`

Compare Source

🧾 Release notes

Features

Client export directive #36470 (320efb7)

Chores

update dependency microbundle to ^0.15.1 for gatsby-link #36512 (0e56ad6)

`v4.22.0`

Compare Source

🧾 Release notes

Note: Version bump only for package gatsby-link

`v4.21.0`

Compare Source

🧾 Release notes

Bug Fixes

Correctly export default for CJS #36312 (abb0baa)

Chores

update dependency del-cli to v5 for gatsby-link #36287 (272b419)

`v4.20.0`

Compare Source

🧾 Release notes

Bug Fixes

Update resolve import resolve #36229 (b125296)
Publish types #36199 (6d6f034)

4.19.1 (2022-07-21)

Features

Publish some packages as ESM & CJS #36012 (5bd3063)

4.18.1 (2022-07-12)

Note: Version bump only for package gatsby-link

`v4.18.1`

Compare Source

Note: Version bump only for package gatsby-link

`v4.18.0`

Compare Source

🧾 Release notes

Bug Fixes

use proper babelrc configs for compiling packages #35948 (384e801)

Configuration

📅 Schedule: Branch creation - "every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

Jul 05 '22 23:07 renovate[bot]

Branch automerge failure

This PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead.

Branch has one or more failed status checks

Jul 05 '22 23:07 renovate[bot]