Skip to content

chore(release): prepare 0.1.0 - #84

Merged
imanimanyara merged 4 commits into
mainfrom
release/0.1.0-prep
Oct 31, 2026
Merged

imanimanyara merged 4 commits into
mainfrom
release/0.1.0-prep

Conversation

@imanimanyara

Copy link
Copy Markdown
Contributor

Summary

Release prep for v0.1.0 of ichava/icon-sets-flag. Reversible only: no tag, no history change.

  • CHANGELOG: [Unreleased] is closed into ## [0.1.0] - TBD with a short intro; the folded post-reset 0.1.x sections move, unchanged and one level down, under ## [Archived history] above the pre-reset sections.

  • release-please: .release-please-manifest.json and config.json package.version are 0.1.0; bootstrap-sha is removed because it names a commit the squash removes.

  • composer.json: author is Simtabi LLC at the role address opensource@simtabi.com (was ichava@simtabi.com), description states what ships; no version field; NoPersonalContactTest pins the new address.

  • README: docs standard for 0.1.0 (badges only where true, Install, ## Quick start guide and usage with Getting started and Usage). docs/installation.md no longer says nothing is on Packagist.

  • The pack is listed on Packagist, so the README gains the Packagist badge (with Tests, Static analysis and MIT). Install keeps a repositories block only for the laranail/* packages core needs, which are not on Packagist yet.

Release flow

The repository is to be published as one root commit and tagged v0.1.0 by hand (see the release checklist). The tag starts release.yml, whose extractor publishes the ## [0.1.0] section as the release body and fails closed without it, which is why the section is closed here rather than by release-please. After the tag, release-please reads v0.1.0 as the last release, so its next pull request is 0.1.1. Until the squash, the Monday 11:00 UTC release-please run may open a "release 0.1.1" pull request off the old v0.1.0 tag; close it unmerged. The TBD date can be set in the last pre-squash change; the extractor does not read the heading line.

Verification

  • Extractor dry-run for 0.1.0: non-empty section, stops before the archive. changelog.yml order and duplicate check: pass.
  • As CI runs them, with ichava/core aliased from main (f1c1648): composer validate --strict, composer pint, PHPStan (level max, --debug, the sandbox refuses the worker port), vendor/bin/pest: green.

The manifest and config.json package.version move to 0.1.0, the version the repository is tagged at when it is published as a single commit. bootstrap-sha is removed because it names a commit that publishing removes; after the tag, release-please reads v0.1.0 as the last release.
Badges only where true, an Install section that names the laranail repositories core needs, and a Quick start guide and usage section.
The v0.1.0 tag is cut by hand on the published commit, so release-please never closes [Unreleased] for it and release.yml fails closed without a [0.1.0] section. The folded 0.1.x sections move under Archived history, unchanged.
The author is Simtabi LLC at the community role address opensource@simtabi.com, and the description states what the pack ships.
@imanimanyara
imanimanyara merged commit a00b73e into main Oct 31, 2026
10 checks passed
@imanimanyara
imanimanyara deleted the release/0.1.0-prep branch October 31, 2026 12:00
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