chore: prepare 0.0.16 release

Author: github-actions[bot]

.github/workflows/publish.yml

@@ -37,6 +37,7 @@ jobs:
       - name: Build package
         run: bun run build
 
+      # This is the only workflow that publishes the package to npm.
       - name: Publish to npm
         run: npm publish --provenance --access public
         working-directory: packages/astro-gravatar

.github/workflows/release.yml

@@ -23,6 +23,8 @@ jobs:
           fetch-depth: 0
           token: ${{ secrets.GITHUB_TOKEN }}
 
+      # This workflow prepares version/changelog metadata and release artifacts.
+      # It does not publish to npm directly; tagged publishes happen in publish.yml.
       - name: Sampo Release
         id: sampo
         uses: bruits/sampo/crates/sampo-github-action@main

.sampo/changesets/add-oidc-publish-workflow.md

@@ -33,6 +33,8 @@ alwaysApply: false
 - Run coverage enforcement: `bun run test:coverage`
 - Build the package: `bun run build`
 - Preview publish contents: `cd packages/astro-gravatar && bun pm pack --dry-run`
+- Run full release checks: `bun run release:check`
+- Preview the next Sampo release: `bun run sampo:preview`
 - Build docs explicitly: `cd apps/astro-gravatar.and.guide && bun run build`
 
 ## Validation expectations
@@ -80,9 +82,11 @@ alwaysApply: false
 
 - CI currently checks lint, formatting, typechecking, coverage, build, security audit, pack dry-run, and bundle size.
 - Coverage enforcement is implemented by `packages/astro-gravatar/package.json` plus `scripts/check-coverage.ts`.
+- `release.yml` prepares release metadata through Sampo. Treat it as release-prep automation, not the npm publish step.
 - Package publishing is tag-driven through `.github/workflows/publish.yml`.
 - The publish workflow uses `npm publish --provenance --access public` from `packages/astro-gravatar`.
 - Changes that affect the published package should usually include a Sampo release entry via `bun run sampo:add`.
+- The operational release sequence is: `bun run release:check` -> `bun run sampo:add` -> optional `bun run sampo:preview` -> `bun run sampo:release` -> review version/changelog -> push `v<version>` tag -> let `publish.yml` publish to npm.
 
 ## Documentation expectations
 

.sampo/changesets/fix-publish-workflow.md

@@ -97,7 +97,10 @@ bun run typecheck
 bun run test
 bun run test:coverage
 bun run build
-cd packages/astro-gravatar && bun pm pack --dry-run
+bun run release:check
+bun run sampo:add
+bun run sampo:preview
+bun run sampo:release
 ```
 
 ## Documentation
@@ -110,12 +113,25 @@ cd packages/astro-gravatar && bun pm pack --dry-run
 
 ## Release workflow
 
-This repo uses Bun for local validation and a tag-driven GitHub Actions workflow for npm publishing.
+This repo uses Bun for local validation, Sampo for release metadata preparation, and a tag-driven GitHub Actions workflow for actual npm publishing.
 
-1. Run `bun run lint`, `bun run typecheck`, `bun run test`, and `bun run build`.
-2. Confirm publish output with `cd packages/astro-gravatar && bun pm pack --dry-run`.
+1. Run `bun run release:check`.
 3. Add a Sampo release entry when the published package changes: `bun run sampo:add`.
-4. Create and push a version tag like `v0.0.16` to trigger `.github/workflows/publish.yml`.
+4. Run `bun run sampo:preview` if you want to inspect the planned version bump before changing files.
+5. Run `bun run sampo:release` to consume pending release entries and update version/changelog metadata.
+6. Review the resulting package version and `packages/astro-gravatar/CHANGELOG.md`.
+7. Create and push a version tag like `v0.0.16` to trigger `.github/workflows/publish.yml`.
+
+### Workflow responsibilities
+
+- `.github/workflows/release.yml` prepares release metadata with Sampo when `main`, `beta`, or `alpha` changes.
+- `.github/workflows/publish.yml` is the only workflow that actually publishes to npm, and it runs only on `v*` tags using npm Trusted Publishing (OIDC).
+
+### Astro directory listing
+
+- `astro-gravatar` is published as an Astro component package, not an `astro add` integration.
+- After a new npm version is published, Astro's integrations/components directory can pick it up from npm metadata such as `name`, `description`, `homepage`, `repository`, and ecosystem keywords.
+- If the listing needs a custom avatar or metadata override after publish, open an issue with the Astro team using the live npm package as the source of truth.
 
 ## License
 

AGENTS.md

@@ -4,14 +4,15 @@ import starlight from '@astrojs/starlight';
 
 // https://astro.build/config
 export default defineConfig({
+  site: 'https://astro-gravatar.and.guide',
   integrations: [
     starlight({
       title: 'Astro Gravatar',
       social: [
         {
           icon: 'github',
           label: 'GitHub',
-          href: 'https://github.com/your-username/astro-gravatar',
+          href: 'https://github.com/imjlk/astro-gravatar',
         },
       ],
       sidebar: [

README.md

@@ -9,8 +9,8 @@ Get astro-gravatar installed and running in your Astro project.
 
 ## Prerequisites
 
-- Astro project (version 4.0 or higher)
-- Node.js 18+ or Bun
+- Astro project (version 4, 5, or 6)
+- Node.js 22.12+ or Bun
 - Package manager (npm, yarn, pnpm, or Bun)
 
 ## Install Package
@@ -96,7 +96,7 @@ TypeScript types are included automatically. No additional setup needed.
 
 **Module not found error?**
 
-- Ensure you're using Astro 4.0+
+- Ensure you're using a supported Astro version (`^4 || ^5 || ^6`)
 - Restart your development server
 - Check that `node_modules/astro-gravatar` exists
 

apps/astro-gravatar.and.guide/astro.config.mjs

@@ -401,8 +401,8 @@ global.fetch = async function (url, options) {
 
 ### Community Resources
 
-- **GitHub Issues**: [Report bugs and request features](https://github.com/your-username/astro-gravatar/issues)
-- **Discussions**: [Ask questions and share examples](https://github.com/your-username/astro-gravatar/discussions)
+- **GitHub Issues**: [Report bugs and request features](https://github.com/imjlk/astro-gravatar/issues)
+- **Discussions**: [Ask questions and share examples](https://github.com/imjlk/astro-gravatar/discussions)
 - **Gravatar Documentation**: [Official API docs](https://en.gravatar.com/site/implement/api/)
 
 ### Debug Information