chore(release): 1.1.0 - #186
Conversation
8d7f597 to
7a08843
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #186 +/- ##
=======================================
Coverage 83.96% 83.96%
=======================================
Files 138 138
Lines 2988 2988
Branches 564 564
=======================================
Hits 2509 2509
Misses 340 340
Partials 139 139 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
!simple-release/set-preamble ✨ HighlightsSelf-closing tags in rich text (
|
7a08843 to
932b0ef
Compare
nano_kit
1.1.0 (2026-08-03)
✨ Highlights
Self-closing tags in rich text (
@nano_kit/intl)rich(andmapTags) now understand self-closing tags like<br/>and<br />— handy for line breaks and other void elements in translations. Handlers for such tags are called with empty chunks. Unknown self-closing tags are still stripped as markup.Rich tag handlers receive an unique index (
@nano_kit/intl)Every tag handler now gets an unique index as the second argument — use it as a
keyfor framework nodes:No more
keywarnings andChildren.toArray(t.sticker)workarounds in React.Bonus:
mapTagsis now reentrant — nested calls from tag handlers no longer clobber the outer call's parsing state.Features
@nano_kit/intl
1.1.0 (2026-08-03)
✨ Highlights
Self-closing tags in rich text (
@nano_kit/intl)rich(andmapTags) now understand self-closing tags like<br/>and<br />— handy for line breaks and other void elements in translations. Handlers for such tags are called with empty chunks. Unknown self-closing tags are still stripped as markup.Rich tag handlers receive an unique index (
@nano_kit/intl)Every tag handler now gets an unique index as the second argument — use it as a
keyfor framework nodes:No more
keywarnings andChildren.toArray(t.sticker)workarounds in React.Bonus:
mapTagsis now reentrant — nested calls from tag handlers no longer clobber the outer call's parsing state.Features
This PR was generated with simple-release.
📄 Cheatsheet
You can configure the bot's behavior through a pull request comment using the
!simple-release/set-optionscommand.Command Format
Useful Parameters
Bump
versionstringas'major' | 'minor' | 'patch' | 'prerelease'prereleasestringfirstReleasebooleanskipbooleanbyProjectRecord<string, object>Publish
skipbooleanaccess'public' | 'restricted'tagstringUsage Examples
Force specific version
Force major bump
Create alpha pre-release
Publish with specific access and tag
Custom Changelog Preamble
You can add custom markdown to the top of the changelog (right after the version header) using the
!simple-release/set-preamblecommand. The markdown after the command line becomes the preamble.In a monorepo, pass the full package name after the command to target a single package's changelog. Wrap the name in backticks so GitHub keeps it as text instead of a mention:
Use one comment per package, plus one without a name for the whole release.
Access Restrictions
The commands can only be used by users with permissions:
Notes
!simple-release/set-optionscommand takes priority!simple-release/set-preamblecomment per package takes priorityset-optionscommand will be ignored