Skip to content

docs(repo): prepare first public release#1

Merged
fidalgo merged 2 commits into
mainfrom
docs/first-release-readiness
Jul 17, 2026
Merged

docs(repo): prepare first public release#1
fidalgo merged 2 commits into
mainfrom
docs/first-release-readiness

Conversation

@fidalgo

@fidalgo fidalgo commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Document installation, configuration, troubleshooting, contribution, security, conduct, and maintainer release procedures for the public gem.

Refresh checkout hardening, point package metadata at the live repository, and record the complete 0.1.0 release surface without adding one-off release automation.

How to test

Release notes

Does this change need an explicit changelog or release-note callout beyond the PR title?

Checklist

  • PR title is a Conventional Commit and suitable for squash merge
  • Tests added/updated (if applicable)
  • Docs updated (if applicable)
  • I kept changes focused and easy to review
About the maintainers

Built by Ethos Link, the team behind Reviato.
Capture. Interpret. Act.
Turn guest feedback into clear next steps for your team. Collect private appraisals, spot patterns across reviews, and act before small issues turn into public ones.

fidalgo added 2 commits July 17, 2026 10:44
Document installation, configuration, troubleshooting, contribution, security, conduct, and maintainer release procedures for the public gem.

Refresh checkout hardening, point package metadata at the live repository, and record the complete 0.1.0 release surface without adding one-off release automation.
Align the supported Ruby floor with the existing locked dependencies, including parallel 2.x, and replace the failing Ruby 3.1.3 matrix entry with Ruby 3.3.

Update package metadata, documentation, Standard's syntax target, and the initial changelog so consumers and automation share the same compatibility contract.
@fidalgo
fidalgo merged commit 3122a06 into main Jul 17, 2026
6 checks passed
@fidalgo
fidalgo deleted the docs/first-release-readiness branch July 17, 2026 10:20
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