Skip to content

chore(deps): update dependency @netlify/functions to v4 #13838

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

Merged
merged 1 commit into from
Jun 9, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 28, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@netlify/functions ^3.0.0 -> ^4.0.0 age adoption passing confidence

Release Notes

netlify/primitives (@​netlify/functions)

v4.0.0

Compare Source

v3.1.10

Compare Source

v3.1.9

Compare Source

v3.1.8

Compare Source

v3.1.7

Compare Source

v3.1.5

Compare Source

v3.1.4

Compare Source

v3.1.3

Compare Source

v3.1.2

Compare Source

v3.1.1

Compare Source

v3.1.0

Compare Source

v3.0.4

Compare Source

v3.0.3

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source


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 was generated by Mend Renovate. View the repository job log.

Copy link

changeset-bot bot commented May 28, 2025

⚠️ No Changeset found

Latest commit: 5def307

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@svelte-docs-bot
Copy link

@benmccann
Copy link
Member

perhaps best to do with sveltekit 3 since it's potentially breaking?

@benmccann benmccann added this to the 3.0 milestone May 30, 2025
@elliott-with-the-longest-name-on-github
Copy link
Contributor

Wouldn't this just be a major for the adapter?

@benmccann
Copy link
Member

Yeah, but if we wanted to minimize the number of majors it might make sense to do it with SvelteKit 3 - though it's quite possible that wouldn't cause a major version bump on the adapters, but I'm not sure what exactly will be included and no one's clambering for this so we have some time

@renovate renovate bot force-pushed the renovate/netlify-functions-4.x branch from 58b28aa to 5def307 Compare June 9, 2025 01:25
@serhalp
Copy link
Contributor

serhalp commented Jun 9, 2025

Here are the release notes FYI: https://github.com/netlify/primitives/releases/tag/functions-v4.0.0. We had a bit of a hiccup with the release naming when we migrated this package into a monorepo causing Renovate to no longer pick them up automatically, sorry!

4.0.0 is really just reverting engines.node that accidentally got widened in 3.1.0 back to what they were in 3.0.4. I marked it potentially breaking just to be extra safe.

@serhalp
Copy link
Contributor

serhalp commented Jun 9, 2025

... also, wait a second, this is a dev dependency, so merge away!

@benmccann benmccann removed this from the 3.0 milestone Jun 9, 2025
Copy link
Member

@benmccann benmccann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the details!!

@benmccann benmccann merged commit 73cc8a5 into main Jun 9, 2025
18 checks passed
@benmccann benmccann deleted the renovate/netlify-functions-4.x branch June 9, 2025 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants