Update README.md - #32
Merged
Merged
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds a visible README note explaining that OpsHaven is still under active development, should be evaluated on disposable infrastructure before production use, and welcomes community feedback and contributions.
Change type
Motivation
Set clear expectations for early users without implying that the project is unusable, while encouraging testing, bug reports, documentation improvements, and focused contributions.
Related issue: N/A
Implementation details
Added a concise GitHub note near the top of the README:
No product code, workflows, configuration, or security behavior changed.
Security impact
Does this change affect any of the following?
If yes, explain: N/A
Validation performed
Commands/tests executed:
npm testnpm run release:checknpm run securityAdditional validation:
Security considerations
No security assumptions changed. Existing authorization, execution-boundary, audit, rollback, and credential protections remain unchanged because this is a documentation-only update.
Compatibility
Does this change affect:
Documentation
Final checklist