README status line: sections (0.7.1) - #19
Merged
Merged
Conversation
0.7.0 shipped sections but the status line, which craftar.dev checks its claims against, did not mention them.
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
craftar@0.7.1to npm after approval in thenpmenvironment. This is a README-only release, so the npm page shows the current status line.<!-- craftar:section <name> -->…<!-- /craftar:section -->;sectionsand a workspace'soverrides.sections;schema: 2.Test plan
npm run typecheck: pass.npm run build: pass.craftar --versionprints0.7.1.npm test(before the bump): 28 files passed, 1 skipped; 676 passed, 5 skipped. Oracle skipped (no fixture); there is no code change.node-cli-revieweranddocs-authorreviewed the change: both clean, with one optional wording nit left as is.