Skip to content

chore(sync): merge next into beta - #519

Merged
jondricek merged 21 commits into
betafrom
sync/next-to-beta-20261022
Oct 22, 2026
Merged

jondricek merged 21 commits into
betafrom
sync/next-to-beta-20261022

Conversation

@jondricek

Copy link
Copy Markdown
Contributor

Summary

Merge next into beta, preserving source ancestry:

main (synchronized) → next → beta
                            └─ this PR

Source next: 68b426697394703c845e805e17e859c7c8a18847
Destination beta: 7b509bb298aade17bb0c8ca2faa60c1358eaade9

Brings workflow-reference cleanup on object deletion, preservation of creation provenance, UUIDv4 draft bundle IDs, inactive-revision admission handling, current ICS analytic platforms, and development-container/documentation updates. Includes the allowed-values fixture repair already committed on next.

Ancestry finds 20 source commits absent from beta; git cherry finds 15 unmatched non-merge patches and no patch-equivalent commits. These counts include revisions, restoration, and reapplication; they do not describe 20 independent new changes. The resulting merge changes 32 files (+1307/-99) and its tree exactly equals the source tree. No conflicts or additional resolutions.

Evidence

  • Before: beta lacks the source ancestry and resulting changes described above.
  • After: local merge has both branch tips as parents and exactly reproduces next.
  • npm ci, lint, commitlint across the complete beta-to-head range, lockfile and whitespace checks pass. Dependency integrity: 1093 verified signatures, 144 verified attestations.
  • Affected specs: 133 passing. Backreference isolation: 24 passing. Four retry-failing files in isolation: 35 passing. Middleware: 29 passing; scheduler: 15 passing.
  • Full npm test did not pass under Node 22.19.0. Attempt 1: OpenAPI 2, config 22, API 1171 passing / 1 timeout in release-tracks-backrefs. Attempt 2: OpenAPI 2, config 22, API 1148 passing / 5 failures (relationship restoration 401/404, relationship pagination and canonical-domain migration setup 404s, workflow deletion ECONNRESET). Middleware/scheduler ran separately because both full runs stopped at API failures.
  • The user explicitly requested publication and merging after receiving these failure results. No test changes, skips, assertion weakening, or protection bypasses are included.

Merge Danger

Door: two-way

The tree can be reverted with a follow-up commit. Preserve history: merge with a merge commit or ancestry-preserving fast-forward; do not squash or rebase this synchronization.

Blast Radius: API

Object authoring, release-track workflow cleanup/export/admission, allowed-value defaults, and development configuration. Alpha propagation waits until this PR actually merges and remote state is fetched again.

clemiller and others added 21 commits July 6, 2026 13:04
Clean candidate, staged, and quarantine references across snapshot history before permitted object deletion. Preserve member and manifest guards, reconcile surviving latest selectors, and support idempotent cleanup retries.

Add deletion regression coverage and document cleanup and repair semantics.
Replace deterministic UUIDv5 draft bundle generation with random UUIDv4 IDs while preserving stored release bundle IDs. Update bundle regression coverage and export documentation.
Align shared release-track admission with the import lifecycle policy for revoked and deprecated revisions. Preserve exact-revision existence checks, active-content validation, membership, manifests, and exported inactive content.

Add lifecycle admission regression coverage and document the exemption.
Carry creation provenance from the latest stored revision without historical recovery or organization backfill. Fetch only that revision and retain normal authoring and import behavior.

Cover absent and divergent imported provenance, historical STIX preservation, and normal lifecycle synchronization; document the prevention-only contract.
Remove the sync-specific fixture adjustment from PR #518 as requested.
Leave test repairs for next; the seeded Network Devices assertion is
expected to fail until addressed there.
Remove the test option during setup so the lifecycle assertions do not depend on bundled defaults.
Start a normal push range after replacing the unreleased merge history. The previous push referenced a commit absent from the runner checkout.
@jondricek
jondricek merged commit 17f1979 into beta Oct 22, 2026
1 check passed
@codecov-commenter

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

❌ Patch coverage is 91.16279% with 19 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.25%. Comparing base (7b509bb) to head (58362be).
⚠️ Report is 22 commits behind head on beta.

Files with missing lines Patch % Lines
...services/release-tracks/object-deletion-service.js 89.87% 8 Missing ⚠️
app/repository/_base.repository.js 82.35% 3 Missing ⚠️
...release-tracks/release-track-dynamic.repository.js 91.89% 3 Missing ⚠️
...elease-tracks/release-track-registry.repository.js 78.57% 3 Missing ⚠️
app/services/meta-classes/base.service.js 95.91% 1 Missing and 1 partial ⚠️
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             beta     #519      +/-   ##
==========================================
+ Coverage   82.16%   82.25%   +0.08%     
==========================================
  Files         257      258       +1     
  Lines       41661    41833     +172     
  Branches     5554     5608      +54     
==========================================
+ Hits        34232    34410     +178     
+ Misses       7326     7316      -10     
- Partials      103      107       +4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jondricek
jondricek deleted the sync/next-to-beta-20261022 branch October 22, 2026 21:16
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 4.26.0-alpha.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants