Release 1.8.0

[sir-sigurd]

Cuts 1.8.0, releasing the Transit Gateway egress mode (#115).

CHANGELOG-only: adds ## [1.8.0] under [Unreleased] (the TGW [Added] entry becomes 1.8.0) and updates the link refs. Minor bump — the feature is opt-in and non-breaking (new vars default to off/null; existing deployments see no plan diff).

Stacked on #115. Base is tgw-egress-toggle so this captures the TGW changelog entry. Do not merge before #115 — once #115 merges and its branch is deleted, GitHub auto-retargets this PR's base to main, leaving a clean CHANGELOG-only release PR to merge + tag 1.8.0.

Set the [1.8.0] date to the actual merge date before merging (currently a placeholder).

Greptile Summary

This PR cuts the 1.8.0 release by promoting the Transit Gateway egress changelog entry from [Unreleased] into a new ## [1.8.0] section and updating the comparison link refs accordingly.

• Adds ## [1.8.0] - 2026-06-09 with the TGW egress entry (moved from [Unreleased]); [Unreleased] is left empty for future work as expected.
• Updates [Unreleased] compare link from 1.7.2...HEAD to 1.8.0...HEAD and adds a [1.8.0] tag URL, matching the existing link-ref convention.

Confidence Score: 4/5

CHANGELOG-only change; all structural edits (section header, link refs) are correct and consistent with existing entries. The only thing to verify before merging is that the release date matches the actual merge day.

The change is mechanical and low-risk — it promotes one changelog entry and updates two link refs. The sole open item is the date 2026-06-09, which the author themselves flagged as a placeholder; if the PR merges on a different day the recorded release date will be off.

No files require special attention beyond confirming the release date in CHANGELOG.md is updated to the actual merge date.

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds ## [1.8.0] - 2026-06-09 section with the TGW egress entry (moved from [Unreleased]), updates the [Unreleased] compare link to 1.8.0...HEAD, and adds a [1.8.0] tag link ref. Structure and link format match existing entries. Date is currently today's value but the PR description flags it as a placeholder that must be set to actual merge date.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["[Unreleased] - YYYY-MM-DD\n(empty, ready for next changes)"]
    B["[1.8.0] - 2026-06-09\nTransit Gateway egress mode"]
    C["[1.7.2] - 2026-06-08\nAWS provider constraint bump"]
    D["[1.7.1] and earlier..."]

    A --> B --> C --> D

    style A fill:#f9f,stroke:#999
    style B fill:#9cf,stroke:#36a,color:#000

Loading

_{Reviews (1): Last reviewed commit: "Release 1.8.0" | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

Placeholder date may need updating before merge

The PR description explicitly notes that 2026-06-09 is a placeholder and asks for the actual merge date to be set before merging. The current value happens to match today's date, so it is correct if merged today — but if this PR sits open and merges on a later date, the release date will be wrong in the changelog history.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!