Skip to content

chore(deps): bump ghcr.io/devcontainers/features/node from 1.7.1 to 2.0.0#184

Open
dependabot[bot] wants to merge 4 commits into
mainfrom
dependabot/devcontainers/ghcr.io/devcontainers/features/node-2.0.0
Open

chore(deps): bump ghcr.io/devcontainers/features/node from 1.7.1 to 2.0.0#184
dependabot[bot] wants to merge 4 commits into
mainfrom
dependabot/devcontainers/ghcr.io/devcontainers/features/node-2.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 4, 2026

Copy link
Copy Markdown
Contributor

Bumps ghcr.io/devcontainers/features/node from 1.7.1 to 2.0.0.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

unclesp1d3r and others added 4 commits May 1, 2026 22:54
…ing docs (#179)

## Summary

Pre-release documentation hygiene pass. Removes user-facing docs that
describe features users can't actually use yet (the product hasn't
shipped a v1.0.0 release) and scrubs paid-tier specifics that violate
AGENTS.md's open-core hygiene rules. Follows the eight-phase workflow
documented at
`docs/solutions/workflow-issues/open-core-hygiene-confluence-migration-2026-04-18.md`.

Equivalent commercial-tier and user-facing content is preserved in
Confluence space ES (verified per file before deletion).

## Commits

1. `547b47f` — **Remove aspirational user-facing docs**
(install/deployment/operator/API/CLI). 11 markdown files deleted under
`docs/src/{deployment,user-guides,api-reference}/` plus orphaned
`docs/src/cli-reference.md`. SUMMARY.md / introduction.md /
getting-started.md / project-overview.md updated to drop or rewrite
dangling links.
2. `928ea19` — **Scrub paid-tier specifics from steering and spec
docs.** Deletes `.kiro/steering/product.md` (pure paid-tier overview),
`spec/structure.md`, `spec/tech.md` (older duplicates of the steering
versions). Edits `.kiro/steering/structure.md` and
`.kiro/steering/tech.md` to drop phantom `security-center/` directory,
Free/Business/Enterprise tier enumeration, Business/Enterprise DB
tables, and the Kernel Monitoring (Enterprise Tier) and Enterprise
Security Features subsections — replaced with single
boundary-acknowledgement footnotes.
3. `f8104b8` — **Remove Enterprise Tier subsection from root
SECURITY.md.** Reframed as "Planned Hardening (Community Tier)" with
only items actually planned for the OSS tier; added a single boundary
footnote for fleet-level mTLS.
4. `52d59f4` — **Trim residual paid-tier mentions** in
`project-overview.md` (Organizational Context tier mapping;
Cross-Platform Support entries that mislabeled OSS sysinfo collection as
Enterprise tier) and `security_design_overview.md` (SC-36 Distributed
Processing federated-SC implementation note).

## Verification

- Final grep sweep confirms all remaining "tier" mentions in tracked OSS
docs are boundary footnotes (the preferred pattern from the hygiene
workflow), not paid-tier feature claims.
- All deleted user-facing docs have equivalents in Confluence ES
(Installation 1802370, Docker 1802371, Kubernetes 1802372, Configuration
1802373/1802375, Core API 1802366, CLI 1802368, Feature Tiers 1802352,
Business Tier 1802362, Enterprise Tier 1802363, Architecture Overview
1802349, Security Design Overview 1802346/1802364).
- The canonical PRD covering all tiers is the new Confluence page
11599874.

## Test plan

- [ ] CI passes (linter / mdformat / pre-commit hooks all green locally)
- [ ] `mdbook build` (if relevant CI step exists) succeeds with the
trimmed SUMMARY.md
- [ ] Reviewer manually verifies no surviving paid-tier feature *claims*
(boundary footnotes are intentional)
- [ ] Reviewer confirms deleted docs have Confluence equivalents

## AI Disclosure

Used Claude Code (Claude Opus 4.7 (1M Context)) to inventory pollution,
plan the four-commit structure, perform surgical edits, and verify each
phase. All file changes reviewed before commit. Confluence verification
was done by parallel agents reading source-of-truth pages.

---------

Signed-off-by: UncleSp1d3r <unclesp1d3r@evilbitlabs.io>
Co-authored-by: dosubot[bot] <131922026+dosubot[bot]@users.noreply.github.com>
Hey there! 👋

We've noticed that your Mergify configuration is using some deprecated
fields.

No worries—we've got your back! This automated PR updates your config to
align with the newest standards, ensuring everything keeps running
smoothly.

Do not procrastinate! You **must upgrade** your configuration before
**2026-07-16**, otherwise your configuration will stop working.

## What's Changed?

- `queue_rules → autoqueue`: `autoqueue` in `queue_rules` is deprecated.
Use `auto_merge_conditions` in `merge_protections_settings` instead.
(deadline: 2026-07-16)

## Why This Matters

Keeping your configuration up-to-date means you'll benefit from the
latest features and improvements Mergify has to offer. Plus, it helps
prevent any unexpected hiccups down the road.

## Got Questions? We've Got Answers! 🙌

**Is this update safe to merge?**

Absolutely! We've made sure the changes are compatible with your current
setup. Your workflows should continue to work just as before—if not
better!

**Do I need to do anything special after merging?**

Nope! Just merge this PR, and you're all set. If you have any custom
configurations, it's a good idea to give them a quick look to ensure
everything's in order.

**What if I run into issues or have concerns?**

We're here to help! Feel free to [reach out to our support
team](mailto:support@mergify.com) anytime.

Thanks for being awesome and keeping your configuration up-to-date! If
you have any thoughts or need a hand, don't hesitate to let us know.

Happy merging! 🎉

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Bumps [libc](https://github.com/rust-lang/libc) from 0.2.185 to 0.2.186.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/rust-lang/libc/releases">libc's
releases</a>.</em></p>
<blockquote>
<h2>0.2.186</h2>
<h3>Added</h3>
<ul>
<li>Apple: Add <code>KEVENT_FLAG_*</code> constants (<a
href="https://redirect.github.com/rust-lang/libc/pull/5070">#5070</a>)</li>
<li>Linux: Add <code>PR_SET_MEMORY_MERGE</code> and
<code>PR_GET_MEMORY_MERGE</code> (<a
href="https://redirect.github.com/rust-lang/libc/pull/5060">#5060</a>)</li>
</ul>
<h3>Changed</h3>
<ul>
<li>CI: Migrate FreeBSD CI from Cirrus CI to GitHub Actions (<a
href="https://redirect.github.com/rust-lang/libc/pull/5058">#5058</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/rust-lang/libc/blob/0.2.186/CHANGELOG.md">libc's
changelog</a>.</em></p>
<blockquote>
<h2><a
href="https://github.com/rust-lang/libc/compare/0.2.185...0.2.186">0.2.186</a>
- 2026-04-24</h2>
<h3>Added</h3>
<ul>
<li>Apple: Add <code>KEVENT_FLAG_*</code> constants (<a
href="https://redirect.github.com/rust-lang/libc/pull/5070">#5070</a>)</li>
<li>Linux: Add <code>PR_SET_MEMORY_MERGE</code> and
<code>PR_GET_MEMORY_MERGE</code> (<a
href="https://redirect.github.com/rust-lang/libc/pull/5060">#5060</a>)</li>
</ul>
<h3>Changed</h3>
<ul>
<li>CI: Migrate FreeBSD CI from Cirrus CI to GitHub Actions (<a
href="https://redirect.github.com/rust-lang/libc/pull/5058">#5058</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/rust-lang/libc/commit/42620ffc4109dc32e02f1cae9e63a3f4311b4b71"><code>42620ff</code></a>
[0.2] libc: Release 0.2.186</li>
<li><a
href="https://github.com/rust-lang/libc/commit/9db2eaaaaea60e0b048785e41ca4eb9c50d30ad5"><code>9db2eaa</code></a>
apple: add KEVENT_FLAG_* constants</li>
<li><a
href="https://github.com/rust-lang/libc/commit/38409392ffb50288aa84e94b75fc37bd565fd5bc"><code>3840939</code></a>
Add PR_SET_MEMORY_MERGE and PR_GET_MEMORY_MERGE for linux</li>
<li><a
href="https://github.com/rust-lang/libc/commit/f697deb9440a8f916ec2fb95bef9e06fc847b6f7"><code>f697deb</code></a>
chore: migrate from Cirrus CI to GHA</li>
<li>See full diff in <a
href="https://github.com/rust-lang/libc/compare/0.2.185...0.2.186">compare
view</a></li>
</ul>
</details>
<br />

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps ghcr.io/devcontainers/features/node from 1.7.1 to 2.0.0.

---
updated-dependencies:
- dependency-name: ghcr.io/devcontainers/features/node
  dependency-version: 2.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file devcontainers_package_manager Pull requests that update devcontainers_package_manager code labels May 4, 2026
@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label May 4, 2026
mergify[bot]
mergify Bot previously approved these changes May 4, 2026

@mergify mergify Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Automatically approved by Mergify

@mergify

mergify Bot commented May 4, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Full CI must pass

Wonderful, this rule succeeded.

All CI checks must pass. Activates for non-bot authors, or dependabot when files exist outside .github/workflows/.

  • check-success = DCO
  • check-success = coverage
  • check-success = quality
  • check-success = test
  • check-success = test-cross-platform (macos-15, macOS)
  • check-success = test-cross-platform (ubuntu-22.04, Linux)
  • check-success = test-cross-platform (windows-2022, Windows)

🟢 Do not merge outdated PRs

Wonderful, this rule succeeded.

Make sure PRs are within 3 commits of the base branch before merging

  • #commits-behind <= 3

@unclesp1d3r unclesp1d3r dismissed mergify[bot]’s stale review June 10, 2026 01:31

The merge-base changed after approval.

@mergify mergify Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Automatically approved by Mergify

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file devcontainers_package_manager Pull requests that update devcontainers_package_manager code size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant