This repository was archived by the owner on Oct 9, 2026. It is now read-only.
Repository navigation
Revise README for Boundary CE archiving - #6788
Merged
Merged
Conversation
Updated README to reflect the archiving of Boundary Community Edition and the focus on HCP Boundary and Boundary Enterprise. Added notes on the repository's read-only status and the lack of future updates for Boundary CE.
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
There was a problem hiding this comment.
🟢 Approval recommended
The documentation accurately communicates the archival, with only a minor grammatical correction noted.
1 open finding
What changed in this PR
Updates the README to announce the archival of Boundary Community Edition.
Changes:
- Replaces setup documentation with archival and support guidance.
- Directs users toward HCP Boundary and Boundary Enterprise.
| File | Description |
|---|---|
README.md |
Documents CE archival, read-only status, and lack of planned updates. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| seriously. If you believe you have found a security issue in Boundary, | ||
| _please responsibly disclose_ by contacting us at | ||
| [security@hashicorp.com](mailto:security@hashicorp.com). | ||
| Boundary Community Edition (CE) is no longer under active development, and this repository has been archived. Future Boundary development will focus on HCP Boundary and Boundary Enterprise, where we can provide enterprise grade human and agentic access capabilities. |
irenarindos
approved these changes
Oct 9, 2026
learhy
marked this pull request as draft
October 9, 2026 16:42
Updated the archive notice to include the date of archiving.
irenarindos
approved these changes
Oct 9, 2026
learhy
marked this pull request as ready for review
October 9, 2026 16:46
irenarindos
approved these changes
Oct 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated README to reflect the archiving of Boundary Community Edition and the focus on HCP Boundary and Boundary Enterprise. Added notes on the repository's read-only status and the lack of future updates for Boundary CE.
Description
PCI review checklist
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.