@vdaluz/astro-affiliate 0.5.0 → 0.5.1

package/README.md

@@ -6,12 +6,16 @@ Affiliate links need FTC-compliant disclosure, per-channel tracking tags for rep
 
 ## Install
 
-Pinned https tarball from a tag (no registry needed):
+```
+npm install @vdaluz/astro-affiliate
+```
+
+Alternatively, a pinned https tarball from a tag works too, with no registry involved:
 
 ```jsonc
 // package.json
 "dependencies": {
-  "@vdaluz/astro-affiliate": "https://github.com/vdaluz/astro-affiliate/archive/refs/tags/v0.4.0.tar.gz"
+  "@vdaluz/astro-affiliate": "https://github.com/vdaluz/astro-affiliate/archive/refs/tags/v0.5.1.tar.gz"
 }
 ```
 
@@ -19,9 +23,7 @@ Pinned https tarball from a tag (no registry needed):
 > shorthand (and even an explicit `git+https://` URL) to `git+ssh://` in the lockfile.
 > CI runners (e.g. Cloudflare Pages/Workers) have no SSH key, so `npm ci` would fail to
 > clone it. The `/archive/refs/tags/<tag>.tar.gz` URL is anonymous https with an integrity
-> hash in the lockfile, it just works in CI. Bump the tag in the URL to upgrade. This is the
-> only supported install path; there's no npm registry package (tag-tarball works for anyone,
-> no registry auth needed).
+> hash in the lockfile, it just works in CI. Bump the tag in the URL to upgrade.
 
 Peer dependency: `astro` >= 6.
 
@@ -172,7 +174,7 @@ import { affiliate } from '../config/affiliate';
 </AffiliateLink>
 ```
 
-Renders `target="_blank" rel="noopener noreferrer sponsored"` by default. Pass `class` to style it.
+Renders `target="_blank" rel="noopener noreferrer sponsored"` by default. Pass `class` to style it, or `channel` to target a per-channel tag/link (see [Per-channel tags](#per-channel-tags-reposts-syndication)) - falls back to the program's default when omitted or unconfigured for that channel.
 
 ## Disclosure (`<AffiliateDisclosure>`)
 
@@ -228,17 +230,6 @@ This is a component library, not a drop-in catalog. Each consuming app owns:
   [`@vdaluz/astro-blog`'s `tokens.example.css`](https://github.com/vdaluz/astro-blog) for the
   full token set these sites already share.
 
-## Release process
-
-Tag-pinned tarballs, no registry:
-
-1. Test before tagging: `npm pack`, install the tarball into a scratch Astro app (or one of the
-   consumers locally), `astro check && astro build`.
-2. Bump `version` in `package.json`, commit.
-3. Tag `vX.Y.Z` and push the tag. **The tag must be public before any consumer CI references
-   it**, the tarball URL 404s otherwise.
-4. Bump the tag in each consumer's `package.json` dependency URL.
-
 ## Contributing
 
 Issues welcome. PRs by discussion - open an issue first for anything beyond a typo or docs fix.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vdaluz/astro-affiliate",
-  "version": "0.5.0",
+  "version": "0.5.1",
   "description": "FTC-compliant affiliate-link catalog resolver and disclosure components - proven in production on vdaluz.com and imperfectsystems.com.",
   "keywords": [
     "astro",

package/src/components/AffiliateLink.astro

@@ -6,11 +6,13 @@ interface Props {
   config: AffiliateConfig;
   /** Flat catalog key, e.g. 'atomicHabits'. */
   affiliateKey: string;
+  /** Per-channel tag/link override, e.g. 'medium'. Falls back to the program's default. */
+  channel?: string;
   class?: string;
 }
 
-const { config, affiliateKey, class: className } = Astro.props;
-const { url } = resolveAffiliate(config, affiliateKey);
+const { config, affiliateKey, channel, class: className } = Astro.props;
+const { url } = resolveAffiliate(config, affiliateKey, channel);
 ---
 
 <a href={url} target="_blank" rel="noopener noreferrer sponsored" class={className}>