@outbuild-company/schedule-core 1.26.0 → 1.27.0-experiment.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -95,6 +95,7 @@ the complete `ChangeSet`; a rejected mutation leaves state untouched.
95
95
  ```ts
96
96
  {
97
97
  dataDate: null,
98
+ scheduleAutomaticallyOnDateChange: false,
98
99
  outOfSequencePolicy: 'retained_logic',
99
100
  dependencyReference: 'correlative_id',
100
101
  useExpectedFinishDates: true,
@@ -183,3 +184,20 @@ npm run docs:check
183
184
 
184
185
  The package emits ESM, CommonJS, type declarations, source maps and a browser
185
186
  IIFE. It has no runtime dependencies.
187
+
188
+ ## Releases
189
+
190
+ Every merge to `main` publishes the official version to npm under `latest`.
191
+
192
+ To try a change in the experiment environment before it ships:
193
+
194
+ 1. Open a PR from your feature branch to `experiment` and merge it. CI runs
195
+ lint only and publishes a prerelease such as `1.27.0-experiment.3` under the
196
+ `experiment` dist-tag.
197
+ 2. Pin that exact version in the monorepo's `experiment-schedule` branch.
198
+ 3. Once it works, open a PR from the same feature branch to `main`. The full
199
+ suite runs and the merge publishes the official version.
200
+
201
+ `experiment` is never merged into `main`. After every official release CI merges
202
+ `main` back into `experiment`, so prereleases always carry everything already
203
+ shipped. Prerelease versions never go into the monorepo's `main`.