release-notes
Skill5k starsChanged 5 days agoApache-2.0View on GitHub
Create, curate, or translate BootstrapBlazor release notes in English and Chinese from GitHub-generated notes or user-provided change data. Use for versioned release-note tasks in this repository.
187 other projects use a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- rohaquinlop/dsh-setuptheir own version, first seen Nov 16, 2026
- theyashgupta/dispatchtheir own version, first seen Nov 16, 2026
- xmartlabs/agent-skillstheir own version, first seen Nov 16, 2026
- yearzen1/LocalSkillManagertheir own version, first seen Nov 16, 2026
- fworks-tech/agenthoodtheir own version, first seen Nov 15, 2026
- neomjs/neo-agent-skillstheir own version, first seen Nov 15, 2026
Who's talking about dotnetcore/BootstrapBlazor
- dotnet/aspnetcore“[dotnet-sdk-10.0.100-preview.1.25103.13] Apps retarget failed with error "The following scoped CSS bundles …”GitHub · Feb 10, 2025 · 2 reactions
- YoussefWaelMohamedLotfy/TeleQ“Bump BootstrapBlazor from 11.0.1 to 11.0.2”GitHub · Nov 2, 2026
- YoussefWaelMohamedLotfy/TeleQ“Bump BootstrapBlazor from 10.10.2 to 11.0.0”GitHub · Oct 8, 2026
- YoussefWaelMohamedLotfy/TeleQ“Bump BootstrapBlazor from 10.10.0 to 10.10.1”GitHub · Sep 7, 2026
- qin-guan/Homer“Bump the minor group with 6 updates”GitHub · May 12, 2026
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub (50 times).
On GitHub · 50
- Feb 10, 2025[dotnet-sdk-10.0.100-preview.1.25103.13] Apps retarget failed with error "The following scoped CSS bundles do not have matching endpoints" — dotnet/aspnetcore2 reactions · 7 comments
- Nov 2, 2026Bump BootstrapBlazor from 11.0.1 to 11.0.2 — YoussefWaelMohamedLotfy/TeleQ0 reactions · 1 comment
- Oct 8, 2026Bump BootstrapBlazor from 10.10.2 to 11.0.0 — YoussefWaelMohamedLotfy/TeleQ0 reactions · 1 comment
- Sep 7, 2026Bump BootstrapBlazor from 10.10.0 to 10.10.1 — YoussefWaelMohamedLotfy/TeleQ0 reactions · 1 comment
- May 12, 2026Bump the minor group with 6 updates — qin-guan/Homer0 reactions · 1 comment
45 more on GitHub
- Apr 29, 2026Bump the minor group with 1 update — qin-guan/Homer0 reactions · 1 comment
- Apr 22, 2026Bump the minor group with 20 updates — qin-guan/Homer0 reactions · 1 comment
- Apr 21, 2026Bump the minor group with 20 updates — qin-guan/Homer0 reactions · 1 comment
- Apr 15, 2026Bump the minor group with 18 updates — qin-guan/Homer0 reactions · 1 comment
- Apr 14, 2026Bump the minor group with 18 updates — qin-guan/Homer0 reactions · 1 comment
- Apr 8, 2026Bump the minor group with 18 updates — qin-guan/Homer0 reactions · 1 comment
- Mar 31, 2026Bump the minor group with 18 updates — qin-guan/Homer0 reactions · 1 comment
- Mar 27, 2026Bump the minor group with 18 updates — qin-guan/Homer0 reactions · 1 comment
- Mar 23, 2026Bump the minor group with 16 updates — qin-guan/Homer0 reactions · 1 comment
- Mar 16, 2026Bump the minor group with 7 updates — qin-guan/Homer0 reactions · 1 comment
- Mar 12, 2026Bump the minor group with 7 updates — qin-guan/Homer0 reactions · 1 comment
- Mar 11, 2026Bump the minor group with 7 updates — qin-guan/Homer0 reactions · 1 comment
- Mar 10, 2026Bump the minor group with 4 updates — qin-guan/Homer0 reactions · 1 comment
- Mar 2, 2026Bump the minor group with 1 update — qin-guan/Homer0 reactions · 1 comment
- Feb 25, 2026Bump the minor group with 1 update — qin-guan/Homer0 reactions · 1 comment
- Feb 13, 2026Bump the minor group with 1 update — qin-guan/Homer0 reactions · 2 comments
- Feb 11, 2026Bump the minor group with 8 updates — qin-guan/Homer0 reactions
- Feb 10, 2026Bump the minor group with 7 updates — qin-guan/Homer0 reactions · 1 comment
- Feb 5, 2026Bump the minor group with 1 update — qin-guan/Homer0 reactions · 1 comment
- Jan 30, 2026Bump the minor group with 1 update — qin-guan/Homer0 reactions · 1 comment
- Jan 26, 2026Bump the minor group with 11 updates — qin-guan/Homer0 reactions
- Jan 22, 2026Bump the minor group with 11 updates — qin-guan/Homer0 reactions · 1 comment
- Jan 21, 2026Bump the minor group with 11 updates — qin-guan/Homer0 reactions · 1 comment
- Jan 13, 2026Bump the minor group with 6 updates — qin-guan/Homer0 reactions · 1 comment
- Jan 7, 2026Bump the minor group with 1 update — qin-guan/Homer0 reactions · 1 comment
- Dec 29, 2025Bump BootstrapBlazor from 10.1.3 to 10.2.0 — YoussefWaelMohamedLotfy/Brite-Task0 reactions · 1 comment
- Dec 29, 2025Bump the minor group with 1 update — qin-guan/Homer0 reactions · 1 comment
- Dec 22, 2025Bump BootstrapBlazor from 10.1.3 to 10.1.4 — YoussefWaelMohamedLotfy/Brite-Task0 reactions · 1 comment
- Dec 22, 2025Bump the minor group with 1 update — qin-guan/Homer0 reactions · 1 comment
- Dec 3, 2025Bump the minor group with 4 updates — qin-guan/Homer0 reactions · 1 comment
- Nov 24, 2025Bump the minor group with 23 updates — qin-guan/Homer0 reactions · 1 comment
- Nov 21, 2025Bump the minor group with 22 updates — qin-guan/Homer0 reactions · 1 comment
- Nov 19, 2025Bump the minor group with 22 updates — qin-guan/Homer0 reactions · 1 comment
- Nov 17, 2025Bump BootstrapBlazor from 10.0.0 to 10.0.1 — YoussefWaelMohamedLotfy/Brite-Task0 reactions · 1 comment
- Nov 17, 2025Bump the minor group with 22 updates — qin-guan/Homer0 reactions · 1 comment
- Nov 10, 2025Bump BootstrapBlazor from 9.11.4 to 9.12.1 — YoussefWaelMohamedLotfy/Brite-Task0 reactions · 1 comment
- Nov 3, 2025Bump BootstrapBlazor from 9.11.4 to 9.12.0 — YoussefWaelMohamedLotfy/Brite-Task0 reactions · 1 comment
- Sep 25, 2025Bump the minor group with 21 updates — qin-guan/Homer0 reactions · 1 comment
- Sep 23, 2025Bump the minor group with 21 updates — qin-guan/Homer0 reactions · 1 comment
- Sep 22, 2025Bump BootstrapBlazor from 9.10.1 to 9.10.2 — YoussefWaelMohamedLotfy/Brite-Task0 reactions · 1 comment
- Sep 19, 2025Bump the minor group with 21 updates — qin-guan/Homer0 reactions · 1 comment
- Sep 2, 2025Bump BootstrapBlazor from 9.9.3 to 9.10.0 — YoussefWaelMohamedLotfy/Brite-Task0 reactions · 1 comment
- Aug 26, 2025Bump BootstrapBlazor from 9.9.2 to 9.9.3 — YoussefWaelMohamedLotfy/Brite-Task0 reactions · 1 comment
- Jan 10, 2025[dotnet-sdk-10.0.100-alpha.1.25057.15] Blazor apps launch with error "Failed to load resource: the server responded with a status of 404()" — dotnet/aspnetcore0 reactions · 6 comments
- Jul 13, 2024Issue: New .NET Foundation Project Application — dotnet-foundation/projects0 reactions · 8 comments
Used with
Projects with it also use brainstorm-experiments-existing, brainstorm-ideas-new and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
skytiger6724Skillbrainstorm-experiments-existing
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Also in 6 projects that use this
skytiger6724Skillbrainstorm-ideas-new
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
Also in 6 projects that use this
45ckSkillpestle-analysis
Also in 6 projects that use this
About-IntelligenceSkillpositioning-ideas
Brainstorm product positioning ideas differentiated from competitors.
Also in 6 projects that use this
About-IntelligenceSkillproduct-name
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.
Also in 6 projects that use this
- +7 more from skytiger6724
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 187
- tw93/Mole★ 75ksame name
- makeplane/plane★ 62ksame name
- tabler/tabler★ 42ksame name
- pnpm/pnpm★ 37ksame name
- quasarframework/quasar★ 27ksame name
- dotnet/core★ 22ksame name
- zauberzeug/nicegui★ 16ksame name
- adobe/react-spectrum★ 16ksame name
- espanso/espanso★ 15ksame name
- formbricks/formbricks★ 13ksame name
177 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 172 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create matching English and Chinese release-note drafts for this repository.
- Distinctive: line 26
If the user supplies a source file or explicit change list, use that as the scope instead of adding unrelated PRs from elsewhere.
- Very specific: line 30
Keep the note concise and user-facing.
- Distinctive: line 32
Do not silently drop a change because a later revert or follow-up appears.
- Distinctive: line 33
When one component or dependency was upgraded several times during the release range, normally report the final version.
- Distinctive: line 34
Do not invent behavior or implementation details beyond the generated notes, linked PR information, or user-confirmed edits.
- Distinctive: line 41
Keep dates, versions, section and entry order, authors, PR links, and Full Changelog links aligned in both files.
- Distinctive: line 43
Use this entry format:
- Distinctive: line 50
Use this document structure:
- Distinctive: line 70
Ensure no unrequested PRs were added and no user edits were lost.
“Common” is measured: kept by at least 6 in 10 of the 172 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
BootstrapBlazor Release Notes
Create matching English and Chinese release-note drafts for this repository. Do not publish a GitHub Release or create a tag.
Gather release data
- Identify the latest published stable release tag from the repository's releases/tags. Do not use prereleases as the baseline unless requested.
- Get the target version from the user's request; if the request says "current version", check the project version. Use the requested release date; if none is given, use the current date.
- Compare the target version with the latest stable version. If the target is not newer, stop and tell the user that no release notes are needed until a newer release tag is available; do not generate notes or create/update files. In particular, a project prerelease for a version that is already stable does not count as a newer release.
Use GitHub's generated release notes as the default source; the user does not need to provide a separate raw file. This step requires the
ghCLI, an authenticated GitHub account (gh auth status), and network access; cloud or CI agents may not have them. Fordotnetcore/BootstrapBlazor, generate notes without creating a release:gh api --method POST repos/dotnetcore/BootstrapBlazor/releases/generate-notes \ -f tag_name=vX.Y.Z \ -f previous_tag_name=vPREVIOUS \ -f target_commitish=main \ --jq .bodyReplace the example tag values with the confirmed target and previous tags. The endpoint returns generated text; it does not publish a release. The GitHub draft page at
https://github.com/dotnetcore/BootstrapBlazor/releases/newcan also generate the same source. If theghCLI, authentication, or GitHub access is unavailable, explain the blocker and use raw change data only if the user provides it.- If the user supplies a source file or explicit change list, use that as the scope instead of adding unrelated PRs from elsewhere.
Curate the changes
- Keep the note concise and user-facing. Organize
fixentries underFixesandfeatentries underFeatures; the Chinese headings are修复and新功能. - Exclude documentation-only and internal maintenance changes from these sections unless the user asks to include them.
- Do not silently drop a change because a later revert or follow-up appears. Inspect the related entries and ask the user when the final shipped behavior is unclear.
- When one component or dependency was upgraded several times during the release range, normally report the final version. Keep PR references that support the summarized change; follow the user's manually curated English version when it differs.
- Do not invent behavior or implementation details beyond the generated notes, linked PR information, or user-confirmed edits.
Write the two files
- Save versioned notes as
ChangeLogs/{version}_en.mdandChangeLogs/{version}_zh.mdat the repository root. CreateChangeLogs/if it does not exist. - Preserve existing files and manually edited content. In particular, do not overwrite an existing English note without explicit instruction.
- Draft English first. Translate the final, user-confirmed English note into Chinese; do not reconstruct the Chinese version independently from older raw data.
- Keep dates, versions, section and entry order, authors, PR links, and Full Changelog links aligned in both files.
- Translate only prose. Preserve component/scope names, commit prefixes, API and parameter identifiers, package names, version numbers, usernames, and URLs.
Use this entry format:
* fix(Component): concise description by @author in https://github.com/dotnetcore/BootstrapBlazor/pull/123 * feat(Component): concise description by @author in https://github.com/dotnetcore/BootstrapBlazor/pull/124Use this document structure:
## Release YYYY-MM-DD VX.Y.Z ### Fixes ... ### Features ... **Full Changelog**: https://github.com/dotnetcore/BootstrapBlazor/compare/vPREVIOUS...vCURRENTIn the Chinese file, translate the section headings and descriptions while retaining the same structure and identifiers.
Final review
- Confirm the title date, version, previous tag, and Full Changelog comparison.
- Compare both files for matching PR IDs, authors, entry counts, and ordering.
- Ensure no unrequested PRs were added and no user edits were lost.
- Report the paths of both files and any unresolved inclusion or release-range decisions.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

