Skip to content

v1.0.3 — Final release (package bump) and CI config alignment

Choose a tag to compare

View all tags
@tobrien tobrien released this 31 Dec 01:10
· 3 commits to working since this release
v1.0.3
cd6c83e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Summary

This release finalizes the 1.0.x release series by removing the development pre-release suffix from package.json (1.0.3-dev.0 → 1.0.3) and aligns repository CI config with an updated kodrdriv schema. The code changes are small and focused: a package version bump and a rename of one CI configuration key. No runtime code or benchmark logic was changed in this set of commits.

What changed (file-level)

  • package.json

    • Version bumped from 1.0.2 to 1.0.3.
    • Context: package.json contains benchmark/test scripts and a prepublishOnly hook; only the version field changed in this release.
    • Diff (relevant lines):
      • "version": "1.0.2",
      • "version": "1.0.3",

  • .kodrdriv/config.yaml

    • Renamed the configuration section and key from release.waitForWorkflows to publish.waitForReleaseWorkflows and retained the boolean value false.
    • Diff (relevant lines):
      • release:
      • waitForWorkflows: false
      • publish:
      • waitForReleaseWorkflows: false

Why these changes were made (rationale & context)

  • Package finalization: The project has been using short-lived pre-release tags (e.g., 1.0.3-dev.0) during the release preparation flow. The commit set that produced this release removes the -dev suffix and sets the official package version to 1.0.3. This is the canonical step that marks the package as a released artifact rather than a development snapshot.

  • CI / automation alignment: The .kodrdriv/config.yaml change renames the key to match a new kodrdriv schema. Commit messages indicate kodrdriv's config schema changed (the new key is publish.waitForReleaseWorkflows) and the repository has been updated to follow that schema while keeping the value false. There are prior commits in the branch that also added a release trigger for the benchmark workflow on published releases; the config rename complements those workflow changes so kodrdriv-managed releases behave as intended under the new schema.

Implications for users and developers

  • End users (consuming the package): There are no API, runtime, or benchmark code changes in this release. The only change affecting package consumers is the published package version number (1.0.3). Consumers that pin or depend on an exact version should expect the final artifact to be available as 1.0.3.

  • CI / Release automation: The kodrdriv configuration now uses publish.waitForReleaseWorkflows: false. The practical effect is that kodrdriv-managed releases will not be blocked by waiting for other workflows to finish (the wait flag remains disabled). The key rename reflects an upstream schema change in kodrdriv; the repository's config now matches that schema.

  • Backward/forward compatibility of tooling: Because the configuration key was renamed to match an updated kodrdriv schema, older versions of kodrdriv (or any automation expecting release.waitForWorkflows) may not read this new key. Conversely, updated kodrdriv versions expect the new key. This means integration behavior for releases may differ depending on the kodrdriv version used by CI operators or third-party tooling.

Relation to previous releases and project evolution

  • Release cadence: The project has a documented pattern in this branch of creating development pre-release tags (e.g., 1.0.1-dev.0, 1.0.2-dev.0, 1.0.3-dev.0) while preparing changes, then committing a final bump that removes the -dev suffix to produce a stable release (1.0.1 → 1.0.2 → 1.0.3). The tag history for the repository shows this pattern.

  • CI improvements previously introduced: Recent commits (visible in the branch's history) added a release trigger to the benchmark workflow so that benchmarks run when a release is published (in addition to push and scheduled runs). The .kodrdriv change in this release is the corresponding config alignment to ensure kodrdriv-managed releases behave consistently with those workflow triggers.

Breaking changes and risk assessment

  • No code-breaking changes detected: Automated checks across the release range (main → HEAD) did not flag any breaking API changes. The release modifies only package metadata and CI configuration—not library source or benchmark logic—so there are no expected breaking changes for library consumers.

  • Potential tooling compatibility risk: The only area with potential for operational impact is the kodrdriv config key rename. If an environment runs an older kodrdriv version that expects release.waitForWorkflows, that older tool will not see publish.waitForReleaseWorkflows, which could change release behavior (for example, whether the release process waits on workflows). This is a tooling compatibility issue rather than an application/API compatibility issue.

Release metadata

  • New package version: 1.0.3 (previous: 1.0.2)
  • Changed files: .kodrdriv/config.yaml, package.json
  • Commits included (HEAD-most recent):
    • chore(release): bump package version to 1.0.3 — Finalize release by removing the -dev suffix (622f2ca)
    • chore(ci): update .kodrdriv config key to publish.waitForReleaseWorkflows — Rename config section to match updated kodrdriv schema (b8dfd02)
    • 1.0.3-dev.0 (tagging step prior to final bump) (e1f1903)
  • Contributors: Tim O'Brien (author of all commits in this range)
  • Diff summary: 3 files changed in the release range (metadata/lockfile and CI config updates); the direct diffs for the two modified files are small as shown above.

Notes for release/automation maintainers

  • The repository's kodrdriv configuration has been updated to match an updated kodrdriv schema; automation that interprets this file should be using a kodrdriv version that recognizes publish.waitForReleaseWorkflows.

  • The package.json retains its existing scripts (benchmark, memory-test, prepublishOnly validating scripts, etc.). The prepublishOnly script remains configured to run validation and tests prior to publish.

Conclusion

This release is a focused maintenance/packaging release: it marks the 1.0.3 package as final and aligns CI configuration with an updated kodrdriv schema. There are no changes to runtime code or benchmarks in this release. The only noteworthy operational consideration is the kodrdriv config key rename, which is a tooling-level compatibility concern rather than an application-level breaking change.

Assets 2
Loading