Skip to content

Execution timestamp setting + new execution IDs feature flag#1857

Merged
bolekk merged 3 commits intomainfrom
flag_for_dontime_timestamps
Feb 27, 2026
Merged

Execution timestamp setting + new execution IDs feature flag#1857
bolekk merged 3 commits intomainfrom
flag_for_dontime_timestamps

Conversation

@bolekk
Copy link
Contributor

@bolekk bolekk commented Feb 26, 2026

Two commits:

  1. Flag (bool) to enable DONTime-based timestamps (needed to perform an atomic feature rollout) - see https://smartcontract-it.atlassian.net/browse/CRE-2081.
  2. Flag (timestamp-based) to atomically roll out new Execution ID format - see https://smartcontract-it.atlassian.net/browse/CRE-1794

(2) needs (1) to be enabled first (see core PR)

@github-actions
Copy link

github-actions bot commented Feb 26, 2026

✅ API Diff Results - No breaking changes


📄 View full apidiff report

@bolekk bolekk changed the title Flag for dontime timestamps Flags for dontime timestamps + new execution IDs feature Feb 26, 2026
@bolekk bolekk force-pushed the flag_for_dontime_timestamps branch from c48e662 to 6944079 Compare February 26, 2026 21:21
@bolekk bolekk changed the title Flags for dontime timestamps + new execution IDs feature Flags for execution timestamps + new execution IDs feature Feb 26, 2026
@bolekk bolekk changed the title Flags for execution timestamps + new execution IDs feature Feature Flags: execution timestamps + new execution IDs Feb 26, 2026
@bolekk bolekk marked this pull request as ready for review February 26, 2026 22:52
@bolekk bolekk requested a review from a team as a code owner February 26, 2026 22:52
@bolekk bolekk changed the title Feature Flags: execution timestamps + new execution IDs Execution timestamp setting + new execution IDs feature flag Feb 26, 2026
@bolekk bolekk requested a review from jmank88 February 27, 2026 01:02
scope: bound.GetScope(),
key: bound.GetKey(),
scope: bound.GetScope(),
isUpperBound: isUpperBound,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit/ isLowerBound would be a bit smoother (and less risky) since the zero value is the old behavior 🤷

@cedric-cordenier
Copy link
Contributor

🤔 Does this mean that adding a new feature flag requires a code change to this schema every time?

@jmank88
Copy link
Contributor

jmank88 commented Feb 27, 2026

🤔 Does this mean that adding a new feature flag requires a code change to this schema every time?

Yes. Deployments needs to understand the schema in order to validate the settings before distributing them. We could maybe skip this repo if we split up cresettings in to sub-sections owned by each repo for themselves, but it would take a lot of additional refactoring in deployments and probably core to make that transition.

@bolekk bolekk enabled auto-merge February 27, 2026 17:42
@bolekk bolekk added this pull request to the merge queue Feb 27, 2026
Merged via the queue into main with commit d6a7bf1 Feb 27, 2026
37 of 39 checks passed
@bolekk bolekk deleted the flag_for_dontime_timestamps branch February 27, 2026 17:51
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.

3 participants