An agentic browser harness: an AI side panel & orb in your own logged-in Chrome, Edge, Arc, Brave or even Firefox run by the agent/subscription you already use (Claude Code, Codex, Antigravity). Free, open source, no API key. Also an MCP server.
TypeScript agentic-browseragentic-browsingagy-cliaiai-agentai-browser-extensionai-toolsbrave-extensionbrowser-agentbrowser-automationbrowser-extensionbrowser-usebrowserskillchrome-extensionclaude-codecodexfirefox-addonmcp-servernanobrowserweb-automation
ci(release): read notes from the real tag object, not checkout's stand-in
Shahriard1cd070752dd
diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex f8d3ef9..feb6efc 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -174,7 +174,16 @@ jobs:- name: Release notes# Prefers the text `prepare` wrote into the annotated tag, and falls back to reading# the conventional-commit log when the tag carries none.- run: node scripts/release-notes.mjs "$VERSION" --out "dist/RELEASE_NOTES-$TAG.md"+ #+ # actions/checkout materialises the pushed tag as a lightweight ref, so `cat-file -t`+ # says `commit` and the annotated tag's own message is invisible — which silently+ # published log-generated notes over hand-curated ones in v0.4.10. Re-fetching the+ # ref restores the real tag object.+ run: |+ git fetch --force origin "refs/tags/$TAG:refs/tags/$TAG"+ test "$(git cat-file -t "$TAG")" = tag \+ || echo "::warning::$TAG is lightweight; notes will come from the commit log"+ node scripts/release-notes.mjs "$VERSION" --out "dist/RELEASE_NOTES-$TAG.md"- name: Create the GitHub releaseenv: