Skip to content

tmp: adjust release please config for functions split release #479

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.

Sign up for GitHub

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
Oct 14, 2025
Merged

tmp: adjust release please config for functions split release #479

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions release-please-config.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,9 @@
"packages/ai": {},
"packages/blobs": {},
"packages/cache": {},
"packages/dev": {},
"packages/dev": {
"exclude-paths": ["packages/dev"]
},
Comment on lines +12 to +14
Copy link
Contributor Author

@pieh pieh Oct 14, 2025

Choose a reason for hiding this comment

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

This is meant to be temporary if the major bump of @netlify/dev in #478 we think is too much. I don't have opinion here and just put this in here for demonstration that we can tell release please to not treat changes from the split as breaking change for this package.

This part would definitely need to be reverted - either before merging this adjustment or after reelase

"packages/dev-utils": {},
"packages/edge-functions": {},
"packages/functions/dev": {},
Expand All @@ -24,6 +26,8 @@
"packages/static": {},
"packages/types": {},
"packages/vite-plugin": {},
"packages/vite-plugin-tanstack-start": {}
"packages/vite-plugin-tanstack-start": {
"exclude-paths": ["packages/vite-plugin-tanstack-start/test"]
}
Comment on lines +29 to +31
Copy link
Contributor Author

@pieh pieh Oct 14, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

That part I think can stay - it means that if changes were just in test, it will not be considering the package changed - it will still get patch bump, because vite plugin was bumped

}
}