Bump version to 0.6.88 for JSR deployment with provenance

[Copilot]

Updated package version from 0.6.58 to 0.6.88 in deno.json. JSDoc annotations already exist inline in TypeScript source files (50/60 files). Automatic JSR deployment configured in existing CI workflow triggers on merge to master with provenance support.

Changes

• deno.json: Version 0.6.58 → 0.6.88
• .github/workflows/ci.yml: Added provenance support for JSR publishing
  • Added id-token: write permission for OIDC token generation
  • Added --provenance flag to deno publish command

JSDoc Status

TypeScript source files contain comprehensive JSDoc annotations with parameter docs and examples. No separate configuration needed—TypeScript's built-in JSDoc support is sufficient.

/**
 * Main compiler class for hostlist compilation.
 * Orchestrates the entire compilation process using async operations throughout.
 */
export class FilterCompiler {
    /**
     * @param optionsOrLogger - Compiler configuration options or legacy logger
     * @example
     * const compiler = new FilterCompiler({
     *   logger: customLogger,
     *   events: { onProgress: (e) => console.log(`Progress: ${e.message}`) }
     * });
     */
    constructor(optionsOrLogger?: FilterCompilerOptions | ILogger)
}

Deployment

Merge to master triggers automatic deno publish via GitHub Actions. Package publishes as @jk-com/adblock-compiler@0.6.88 with provenance attestation, establishing verifiable package authenticity and supply chain security.

Provenance

The provenance feature ensures:

• Package builds are verifiable and traceable to specific GitHub Actions runs
• Supply chain security is enhanced through cryptographic attestation
• Users can verify package authenticity through JSR's provenance system

Original prompt

Do we have a jsdoc file? Typescript has jsdoc annotations, if those can be used. Also, bump the version from 0.6.58 to 0.6.88, and deploy to jsr.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[jaypatrick]

@copilot Publishing to jsr should be part of the ci/cd workflow, so we can establish provenance to jsr.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	adblock-compiler	bc35034	Jan 03 2026, 11:33 PM

[Copilot]

@copilot Publishing to jsr should be part of the ci/cd workflow, so we can establish provenance to jsr.

Added provenance support to the JSR publishing workflow in commit bc35034. The workflow now includes:

• id-token: write permission for OIDC token generation
• --provenance flag on deno publish command

This establishes package authenticity and supply chain security by creating verifiable attestations that trace the package to its specific GitHub Actions build.