Skip to content

fix: bump netlify-plugin-nx-skip-build to 0.1.1 - #1509

Open
f22hd wants to merge 1 commit into
netlify:mainfrom
f22hd:bump-nx-skip-build-0.1.0
Open

f22hd wants to merge 1 commit into
netlify:mainfrom
f22hd:bump-nx-skip-build-0.1.0

Conversation

@f22hd

@f22hd f22hd commented Oct 11, 2026 •

Copy link
Copy Markdown
Contributor

Thanks for contributing the Netlify plugins directory!

Are you adding a plugin or updating one?

  • Adding a plugin
  • Updating a plugin

Have you completed the following?

Test plan

Bumps "Skip nx" from 0.0.7 to 0.1.1 (release notes: 0.1.0, 0.1.1). I'm the plugin author.

What changed for plugin users (no breaking changes, same env vars):

  • Fix: the plugin no longer cancels the build when the affected check errors (e.g. CACHED_COMMIT_REF not in the clone, nx not on PATH). Errors now build, so a real deploy is never silently dropped.
  • Zero-config (0.1.1): the project is derived from the site's package directory, then its publish directory, so PROJECT_NAME is now optional (entry description updated). A derived name that isn't an nx project builds instead of being cancelled.
  • nx is resolved from node_modules/.bin and runs with NX_DAEMON=false; the affected list and the decision are logged.
  • New, optional: an nx-skip-build-ignore bin for [build] ignore that skips before dependency install. It's opt-in via netlify.toml and doesn't change the plugin's behaviour.

Testing:

  • The plugin's own suite (eslint, prettier and 17 ava tests, including the existing @netlify/build smoke test) passes on 0.1.1.
  • Ran against a real 19-app nx workspace: a project not in nx show projects --affected is cancelled, an affected one builds, and a lockfile bump builds all.
  • This repo's tests pass for the updated entry (ava --match "*netlify-plugin-nx-skip-build*": 13 passed, including "package should be published").

I don't have a public deploy log on 0.1.1 yet. I'll add one here once it's rolled out.

@f22hd
f22hd requested a review from a team as a code owner October 11, 2026 11:49
@netlify

netlify Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

👷 Deploy request for netlify-plugins pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 92bbb79

@coderabbitai

coderabbitai Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: c8c912a2-3f61-4f6a-9d00-e090c6bec3c8



📥 Commits

Reviewing files that changed from the base of the PR and between 7f546a8 and c457a40.




📒 Files selected for processing (1)
  • site/plugins.json



🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:




Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.





📝 Summary

Summary by CodeRabbit

  • Chores
    • Updated the listed version of the Netlify build-skip plugin from 0.0.7 to 0.1.0. No other user-visible changes are included in this update.
📝 Summary
📝 Summary

Walkthrough

The netlify-plugin-nx-skip-build catalog entry’s version changed from 0.0.7 to 0.1.0.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Bug fix

Suggested reviewers: pieh





Merge Risk: ⚪ Minimal · up to c457a

The catalog now selects the published 0.1.0 release, and its exact package/version resolves. No actionable merge-blocking risk remains.

Architecture Summary

Architecture risk: 🔵 Low · up to c457a

The change affects 1 system.

Changed systems: site

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — site (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

  • observed — Modified behavior in site/plugins.json: The netlify-plugin-nx-skip-build entry’s version changed from 0.0.7 to 0.1.0.



Pre-merge checks | Passed 4 | Failed 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check Warning The title identifies the correct plugin but states a bump to version 0.1.1, while the changeset updates the catalog entry from 0.0.7 to 0.1.0. This makes the title misleading about the implemented ver… Change the title to state that netlify-plugin-nx-skip-build is bumped to 0.1.0, or update the changeset if version 0.1.1 is intended.
✅ Passed checks (4 passed)
Check name Status Explanation
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Description check Passed The description is related to the plugin version update and explains the reported behavior changes and testing. Although it references version 0.1.1 while the changeset records 0.1.0, it remains relev…

Full details: Title check

Explanation

The title identifies the correct plugin but states a bump to version 0.1.1, while the changeset updates the catalog entry from 0.0.7 to 0.1.0. This makes the title misleading about the implemented version.


  • Fix all pre-merge checks with AI
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR





  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@f22hd
f22hd force-pushed the bump-nx-skip-build-0.1.0 branch from c457a40 to 92bbb79 Compare October 11, 2026 12:05
@f22hd f22hd changed the title fix: bump netlify-plugin-nx-skip-build to 0.1.0 fix: bump netlify-plugin-nx-skip-build to 0.1.1 Oct 11, 2026

This branch has not been deployed

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

1 participant