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

Allow users to select the netlify-plugin-nextjs they want to use so that breaking changes made to the latest version don't mess up my work #268

Closed
mannycolon opened this issue May 3, 2021 · 2 comments
Labels
type: feature code contributing to the implementation of a feature and/or user facing functionality

Comments

@mannycolon
Copy link

mannycolon commented May 3, 2021

Is your feature request related to a problem? Please describe.

Today v3.2.2 cause all new deploys to fail (see here: #267) because deploys use the latest version, if we could choose what version to use this could mitigate these kinds of problems.

Describe the solution you'd like
Allow users to choose what version to use.

@lindsaylevine
Copy link

https://github.com/netlify/netlify-plugin-nextjs#faq this is answered here now!

@lindsaylevine lindsaylevine added the type: feature code contributing to the implementation of a feature and/or user facing functionality label May 3, 2021
@lindsaylevine
Copy link

lindsaylevine commented May 3, 2021

in case that link ever changes:

A: Check out the plugin's releases. You can manually install npm install --save @netlify/[email protected] at the last working version. Once a new working release is out, you can uninstall the plugin at this locked version (npm uninstall --save @netlify/plugin-nextjs), which will re-enable Netlify's build system to use the latest plugin version by default.

@mannycolon mannycolon changed the title Allow users to select the netlify-plugin-nextjs the want to use so that breaking changes made to the latest version don't mess up my work Allow users to select the netlify-plugin-nextjs they want to use so that breaking changes made to the latest version don't mess up my work Nov 22, 2021
serhalp pushed a commit that referenced this issue Apr 5, 2024
* fix: ensure fetch cache tags are checked against tag manifest

* feat: use netlify-cache-tag instread of cache-tag

* fix: return false from check stale

* test: add test to catch subsequent revalidate by tags

* test: change cache-tag assertions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature code contributing to the implementation of a feature and/or user facing functionality
Projects
None yet
Development

No branches or pull requests

2 participants