[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@beesolve/analytics-dashboard@0.8.0

Minor Changes

• 4081a01: Add three-tier totals and breakdowns: all (every request, unchanged), real
  (successful HTML page views — sc_content_type LIKE 'text/html%' AND sc_status BETWEEN 200 AND 299), and watch (the active sitemap URL set). Each tier is
  stored in its own namespace (totals#<tier>#…, breakdown#<tier>#…) with its
  own applied-marker namespace, so the tiers are computed, rolled up, and
  backfilled independently and never collide. The all tier's keys are
  byte-identical to before.

  Processor:

  • requiredRecordFields and columnMap now include sc_content_type so the
    real tier can filter by content type. Consumers configuring CloudFront log
    delivery from requiredRecordFields must redeploy to deliver the new column;
    the real tier populates from that point forward (no historical backfill).
  • buildHourlyQuery/runHourlyAthenaQuery accept an optional extraPredicate;
    processHour, applyDailyRollup, and applyMonthlyRollup accept tier and
    force; the hourly/daily/monthly handlers now also compute the real and
    watch tiers.
  • The backfill CLI gains --tier <all|real|watch> (repeatable) and --force
    (reprocess ignoring the applied marker) for one-off tier recomputes.
  • The resolvers (resolveTotalsLive, resolveBreakdownLive,
    classifyBucketState) accept a tier, defaulting to all.
  • New tierPredicates module and Tier/tiers/tierSegment exports.
  • The v1→v2 compaction column map now carries sc-content-type (correctness for
    future compactions).

  Dashboard:

  • The Overview and Breakdowns pages gain a traffic-tier selector (All / Real /
    Sitemap) wired through the URL, threading tier into getOverview and
    getBreakdown.

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.
• Updated dependencies [010a478]
• Updated dependencies [0937ad2]
• Updated dependencies [4081a01]
  • @beesolve/analytics-processor@0.10.0
  • @beesolve/dynamo-helpers@0.2.2
  • @beesolve/helpers@0.2.2
  • @beesolve/lambda-function-url-protection@0.2.1
  • @beesolve/auth-service@0.20.2
  • @beesolve/email-service@0.5.8
  • @beesolve/cdk-constructs@0.9.0
  • @beesolve/lambda-keep-active@2.1.13

@beesolve/analytics-processor@0.10.0

Minor Changes

• 4081a01: Add three-tier totals and breakdowns: all (every request, unchanged), real
  (successful HTML page views — sc_content_type LIKE 'text/html%' AND sc_status BETWEEN 200 AND 299), and watch (the active sitemap URL set). Each tier is
  stored in its own namespace (totals#<tier>#…, breakdown#<tier>#…) with its
  own applied-marker namespace, so the tiers are computed, rolled up, and
  backfilled independently and never collide. The all tier's keys are
  byte-identical to before.

  Processor:

  • requiredRecordFields and columnMap now include sc_content_type so the
    real tier can filter by content type. Consumers configuring CloudFront log
    delivery from requiredRecordFields must redeploy to deliver the new column;
    the real tier populates from that point forward (no historical backfill).
  • buildHourlyQuery/runHourlyAthenaQuery accept an optional extraPredicate;
    processHour, applyDailyRollup, and applyMonthlyRollup accept tier and
    force; the hourly/daily/monthly handlers now also compute the real and
    watch tiers.
  • The backfill CLI gains --tier <all|real|watch> (repeatable) and --force
    (reprocess ignoring the applied marker) for one-off tier recomputes.
  • The resolvers (resolveTotalsLive, resolveBreakdownLive,
    classifyBucketState) accept a tier, defaulting to all.
  • New tierPredicates module and Tier/tiers/tierSegment exports.
  • The v1→v2 compaction column map now carries sc-content-type (correctness for
    future compactions).

  Dashboard:

  • The Overview and Breakdowns pages gain a traffic-tier selector (All / Real /
    Sitemap) wired through the URL, threading tier into getOverview and
    getBreakdown.

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.
• Updated dependencies [010a478]
• Updated dependencies [0937ad2]
  • @beesolve/dynamo-helpers@0.2.2
  • @beesolve/helpers@0.2.2
  • @beesolve/ip-info@0.3.1
  • @beesolve/cdk-constructs@0.9.0
  • @beesolve/lambda-keep-active@2.1.13

@beesolve/cdk-constructs@0.9.0

Minor Changes

• 0937ad2: StaticWebsite now serves real 404 error pages for multi-page applications.

  The mode prop changed from a string union to a discriminated union:

  // Before
  mode: "singlePageApplication"
  mode: "multiPageApplication"
  
  // After
  mode: { type: "singlePageApplication" }
  mode: { type: "multiPageApplication" } // defaults to /404.html with a 404 status
  mode: { type: "multiPageApplication", notFoundPath: "/not-found.html" }
  mode: { type: "multiPageApplication", customErrorPage: false } // pass S3's native 404 through

  Previously mode was accepted but ignored, and every 404 was rewritten to
  /index.html with status 200. That SPA behavior is now applied only for
  singlePageApplication. For multiPageApplication CloudFront returns a real
  404 status (serving /404.html by default) so missing-page traffic can be
  filtered in analytics.

  This is a breaking change to the mode prop shape. As a 0.x package this is
  released as a minor bump.

Patch Changes

• Updated dependencies [010a478]
  • @beesolve/helpers@0.2.2

@beesolve/action-tokens@0.5.6

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.

@beesolve/cdk-email-alarms@0.1.8

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.

@beesolve/dmarc-consumer@0.4.6

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.
• Updated dependencies [010a478]
• Updated dependencies [0937ad2]
  • @beesolve/dmarc-parser@0.1.5
  • @beesolve/dmarc-reports@0.1.8
  • @beesolve/helpers@0.2.2
  • @beesolve/ip-info@0.3.1
  • @beesolve/sqs-handler@0.2.12
  • @beesolve/cdk-constructs@0.9.0

@beesolve/dmarc-dashboard@0.10.9

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.
• Updated dependencies [010a478]
• Updated dependencies [0937ad2]
  • @beesolve/dmarc-consumer@0.4.6
  • @beesolve/dmarc-parser@0.1.5
  • @beesolve/ip-info@0.3.1
  • @beesolve/lambda-function-url-protection@0.2.1
  • @beesolve/auth-service@0.20.2
  • @beesolve/email-service@0.5.8
  • @beesolve/cdk-constructs@0.9.0
  • @beesolve/lambda-keep-active@2.1.13

@beesolve/dmarc-parser@0.1.5

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.

@beesolve/dmarc-reports@0.1.8

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.
• Updated dependencies [010a478]
• Updated dependencies [0937ad2]
  • @beesolve/dmarc-parser@0.1.5
  • @beesolve/cdk-constructs@0.9.0
  • @beesolve/lambda-keep-active@2.1.13

@beesolve/helpers@0.2.2

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.

@beesolve/dynamo-helpers@0.2.2

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.
• Updated dependencies [010a478]
  • @beesolve/helpers@0.2.2

@beesolve/hmac@0.3.4

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.

@beesolve/ip-info@0.3.1

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.
• Updated dependencies [010a478]
  • @beesolve/helpers@0.2.2

@beesolve/lambda-function-url-protection@0.2.1

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.

@beesolve/lambda-keep-active@2.1.13

Patch Changes

• Updated dependencies [0937ad2]
  • @beesolve/cdk-constructs@0.9.0

@beesolve/lint-config@0.3.5

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.

@beesolve/auth-service@0.20.2

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.
• Updated dependencies [010a478]
• Updated dependencies [0937ad2]
  • @beesolve/action-tokens@0.5.6
  • @beesolve/cdk-email-alarms@0.1.8
  • @beesolve/dynamo-helpers@0.2.2
  • @beesolve/helpers@0.2.2
  • @beesolve/sqs-handler@0.2.12
  • @beesolve/cdk-constructs@0.9.0
  • @beesolve/lambda-keep-active@2.1.13

@beesolve/email-service@0.5.8

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.
• Updated dependencies [010a478]
• Updated dependencies [0937ad2]
  • @beesolve/helpers@0.2.2
  • @beesolve/cdk-constructs@0.9.0

@beesolve/email-service-dashboard@0.6.9

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.
• Updated dependencies [010a478]
• Updated dependencies [0937ad2]
  • @beesolve/helpers@0.2.2
  • @beesolve/lambda-function-url-protection@0.2.1
  • @beesolve/auth-service@0.20.2
  • @beesolve/email-service@0.5.8
  • @beesolve/cdk-constructs@0.9.0
  • @beesolve/lambda-keep-active@2.1.13

@beesolve/sqs-handler@0.2.12

Patch Changes

• 010a478: Add a pre-1.0 stability banner to the README. The package is 0.x and under
  active development, so breaking changes can land in any 0.x release without a
  major version bump. The banner is removed when the package reaches 1.0.0.
• Updated dependencies [010a478]
• Updated dependencies [0937ad2]
  • @beesolve/cdk-email-alarms@0.1.8
  • @beesolve/helpers@0.2.2
  • @beesolve/cdk-constructs@0.9.0