Skip to content

docs: add changelog entries for v0.1.1 and v0.2.0#55

Merged
olivrg merged 1 commit into
mainfrom
chore/release-v0.2.0
Jun 9, 2026
Merged

docs: add changelog entries for v0.1.1 and v0.2.0#55
olivrg merged 1 commit into
mainfrom
chore/release-v0.2.0

Conversation

@olivrg

@olivrg olivrg commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Description

Release prep for v0.2.0. Adds the [0.2.0] changelog section for the static upstream headers feature (upstream.headers, shipped in #54) and backfills the [0.1.1] section, which was tagged without a changelog entry. Updates the compare links. No code changes.

Closes #

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (no functional changes)
  • Documentation
  • CI / build / tooling

Packages Affected

  • packages/proxy
  • packages/dashboard
  • packages/python-sdk
  • Root config / monorepo tooling
  • docs/
  • examples/

Checklist

  • I have read CONTRIBUTING.md
  • My code follows the existing style (ESLint + Prettier pass)
  • TypeScript strict mode — no any types or @ts-ignore without justification
  • I have added or updated tests for my changes
  • All CI checks pass (pnpm secrets:scan, pnpm docs:check:ci, pnpm audit --audit-level=high, pnpm build, pnpm lint, pnpm format:check, pnpm typecheck, pnpm test)
  • I have updated documentation if this changes user-facing behavior
  • Commit messages follow Conventional Commits (e.g. feat:, fix:, docs:)

How to Test

  1. Render CHANGELOG.md and confirm the [0.2.0] and [0.1.1] sections read correctly.
  2. Confirm the compare links resolve ([0.2.0] will work once the v0.2.0 tag is pushed).

Additional Context

This PR precedes the v0.2.0 tag — once merged, the tag is pushed against main to trigger the publish workflow. No Closes lines: the feature itself already merged in #54.

The one judgment call is Packages Affected — CHANGELOG.md is repo-root, so none of the options fit perfectly; I marked "Root config / monorepo tooling" as least-wrong with a clarifying comment. If you'd rather, leave all unchecked and note "repo-root CHANGELOG.md" in the description. Either reads fine.

Record the upcoming v0.2.0 release: static upstream headers
(upstream.headers) under Added, and the static-over-caller precedence
plus reserved-header rejection under Security.

Backfill the v0.1.1 section, which was tagged on 2026-06-04 without a
changelog entry despite shipping a user-facing change (clearer
upstream-unreachable error guidance). Update the compare links so each
release points at its predecessor.
@olivrg olivrg merged commit 4f0e4e5 into main Jun 9, 2026
3 checks passed
@olivrg olivrg deleted the chore/release-v0.2.0 branch June 9, 2026 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant