v1.0.6

What's Changed

• Rely on platform deploy config defaults by @johnbeech in #13

Full Changelog: v1.0.5...v1.0.6

v1.0.5

Stable release for template-api cweb package deployment flow.\n\nIncludes the release workflow correction so the package is published once during dev deployment and prod deploys the already-published package version.

v1.0.4

Stable release following validated v1.0.4-rc.2 cweb package deployment flow.

v1.0.4-rc.2

Release candidate to validate cweb release deployment after disabling the legacy tag package workflow.

v1.0.4-rc.1

Release candidate to validate cweb package publish/deploy workflows after PR #12.

1.0.3-rc1

What's Changed

• ci: pass CWEB_CLIENT_TYPE into cweb machine-auth workflows by @johnbeech in #11

Full Changelog: v1.0.2...1.0.3-rc1

v1.0.2

Summary

v1.0.2 improves consumer-facing deployment verification by asserting stack outputs after deployment.

What Changed

• Added post-deployment CI validation step in Check PR:
  • Calls cweb deployments describe --item-id ...
  • Reads deployment.outputs from Management API
  • Fails CI if expected output values drift
• Validated outputs include:
  • ApiBaseUrl
  • OpenAPISpecEndpoint
  • StatusEndpoint
  • ApiGatewayEndpoint (debug, non-empty)

Why

Management/UI consumers should focus on custom-domain endpoints, not raw execute-api URLs. This release adds an explicit automated guardrail to enforce that contract.

Validation

• PR workflow passed with output assertions enabled.
• Deployment output payload confirmed expected values for template-api.dev.connected-web.services URLs.

Notes

This release is intentionally incremental on top of v1.0.1: no deployment model change, only stronger post-deploy correctness checks.

v1.0.1

Summary

v1.0.1 is the migration release that moves template-api to Connected Web package-based deployment via Management API.

What Changed

• Adopted package deployment workflows (cweb package pack/publish/deploy) for CI and release paths.
• Switched CI auth to GitHub Environment machine credentials:
  • CWEB_CLIENT_ID
  • CWEB_CLIENT_SECRET
• Added and standardized package workflows:
  • Check PR package deploy path in dev
  • Package Pre-release
  • Package Release
• Added migration documentation:
  • MIGRATION.md
• Removed deprecated OIDC validation workflow.

Runtime/Stack Alignment

• Stack supports shared-authorizer deploy-time injection pattern.
• Deployment config is resolved from cweb configure outputs in CI.

Validation

Validated through green CI on PR and RC runs, including:

• CDK/unit tests
• package publish/deploy to dev
• post-deployment smoke tests
• API client publish from deployed /openapi

Notes

This release establishes the baseline package-driven flow and environment bootstrapping conventions for future template consumers.

v1.0.1-rc.4

Pre-release verification run after release/dev routing updates.

v1.0.1-rc.3

Semver/versioning fix for release-triggered API client publish workflow.