Repository navigation
chore(release): prepare 0.1.0 - #84
Merged
Merged
Conversation
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.
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
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] - TBDwith 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.jsonandconfig.jsonpackage.versionare0.1.0;bootstrap-shais removed because it names a commit the squash removes.composer.json: author is Simtabi LLC at the role address
opensource@simtabi.com(wasichava@simtabi.com), description states what ships; noversionfield;NoPersonalContactTestpins the new address.README: docs standard for 0.1.0 (badges only where true, Install,
## Quick start guide and usagewith Getting started and Usage).docs/installation.mdno 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
repositoriesblock only for thelaranail/*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.0by hand (see the release checklist). The tag startsrelease.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 readsv0.1.0as 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 oldv0.1.0tag; close it unmerged. TheTBDdate can be set in the last pre-squash change; the extractor does not read the heading line.Verification
changelog.ymlorder and duplicate check: pass.ichava/corealiased frommain(f1c1648):composer validate --strict,composer pint, PHPStan (level max,--debug, the sandbox refuses the worker port),vendor/bin/pest: green.