Skip to content

chore(deps): update devdependency netlify-cli to v21 - autoclosed#196

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/netlify-cli-21.x
Closed

chore(deps): update devdependency netlify-cli to v21 - autoclosed#196
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/netlify-cli-21.x

Conversation

@renovate

@renovate renovate Bot commented May 6, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
netlify-cli ^20.0.3 -> ^21.6.0 age adoption passing confidence

Release Notes

netlify/cli (netlify-cli)

v21.6.0

Compare Source

Features
  • pass mutated config environment variables to functions during local development (#​7325) (17cb26b)

v21.5.2

Compare Source

Bug Fixes
  • ai-context was not able to find catchall due to early filter (#​7320) (653bf7f)

v21.5.1

Compare Source

Bug Fixes

v21.5.0

Compare Source

Features

v21.4.2

Compare Source

Bug Fixes
  • notify activity dev server and double encoding when proxying to preview server (#​7300) (86e539e)

v21.4.1

Compare Source

Bug Fixes

v21.4.0

Compare Source

Features

v21.3.0

Compare Source

Features
Bug Fixes

v21.2.1

Compare Source

Bug Fixes

v21.2.0

Compare Source

Features
  • update recipes to include windsurf rules directory preset (#​7275) (7502e5f)

v21.1.0

Compare Source

Features
  • add new netlify clone command, to clone an existing repo + connected Netlify site in one step (#​7260) (fe9940e)
  • init: prompt to configure build settings in 'no git remote' case (#​7258) (cb881e8)
Bug Fixes

v21.0.1

Compare Source

Bug Fixes

v21.0.0

Compare Source

⚠ BREAKING CHANGES
  • remove support for deprecated netlify-lambda package (#​7236)

The netlify-lambda NPM package was deprecated in Feb 2023. If you are one of the few using this, see the migration guide.

⚠ Potentially breaking changes
run build before deploy (#​7195)

The deploy command now runs the site's configured build command before deployment by default. Previously, this was achieved by passing the --build flag. In other words, --build is no longer needed.

To opt into the previous default behavior, users can now specify netlify deploy --no-build.

👉🏼 Why are we changing this?

This has long been one of the most common sources of confusion with the Netlify CLI. Developers expect a "deploy" command to deploy their project. We're making this change to follow the Principle of Least Surprise and streamline the experience for new users.

Upgrading

👉🏼 (most common) Build and deploy

Remove the --build flag:

netlify deploy --build [...] # before

netlify deploy [...] # after

👉🏼 Separate build and deploy

[!WARNING]
Make sure your deploy command runs in your expected environment, e.g. if you were running FOO=bar netlify build && netlify deploy, make sure FOO is visible to the deploy command, which is now running the build: FOO=bar netlify deploy.

Collapse into one command, if you can:

netlify build && netlify deploy # before

netlify deploy # after

Otherwise, add the --no-build flag:

make spaghetti && netlify deploy # before

make spaghetti && netlify deploy --no-build # after

👉🏼 (rare) Deploy without build step

Add the --no-build flag:

netlify deploy [...] # before (there was no `--build` here)

netlify deploy --no-build [...]
polish and improve deploy command output (#​7250) (795a451)

If you were automatically looking for specific strings in the netlify deploy output, your scripts may stop working. See the above PR for details.

Note that this is not recommended and such changes may not be considered breaking in the future. For stable output that conforms to semantic versioning, use netlify deploy --json.

Features
Bug Fixes

v20.1.1

Compare Source

Bug Fixes

v20.1.0

Compare Source

Features
Bug Fixes

v20.0.4

Compare Source

Bug Fixes

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 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.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented May 6, 2025

Copy link
Copy Markdown

Deploying runtime-compat with  Cloudflare Pages  Cloudflare Pages

Latest commit: 8f297be
Status: ✅  Deploy successful!
Preview URL: https://ef87c27d.runtime-compat.pages.dev
Branch Preview URL: https://renovate-netlify-cli-21-x.runtime-compat.pages.dev

View logs

@renovate renovate Bot force-pushed the renovate/netlify-cli-21.x branch 5 times, most recently from a92bf44 to 94ded02 Compare May 13, 2025 00:42
@renovate renovate Bot force-pushed the renovate/netlify-cli-21.x branch 4 times, most recently from fff4ce9 to d0549de Compare May 19, 2025 18:24
@renovate renovate Bot force-pushed the renovate/netlify-cli-21.x branch 3 times, most recently from 0d8903e to 44127ee Compare June 4, 2025 03:12
@renovate renovate Bot force-pushed the renovate/netlify-cli-21.x branch from 44127ee to 8f297be Compare June 4, 2025 13:06
@renovate renovate Bot changed the title chore(deps): update devdependency netlify-cli to v21 chore(deps): update devdependency netlify-cli to v21 - autoclosed Jun 6, 2025
@renovate renovate Bot closed this Jun 6, 2025
@renovate renovate Bot deleted the renovate/netlify-cli-21.x branch June 6, 2025 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants