Skip to content

Release 1.0.34 — dependency bumps, CI trigger cleanup, and packaging prep

Choose a tag to compare

View all tags
released this 18 Aug 22:37
· 102 commits to working since this release
v1.0.34
967793c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This release finalizes the 1.0.34 stable package and contains a set of developer-focused changes: dependency updates (notably lint rules and React patch alignment), CI workflow refinements to reduce unnecessary runs, and packaging/version housekeeping in package.json. The changes are targeted at maintainers and integrators who run local development, CI, or linting; they do not introduce runtime API features for end users but do affect development and build behavior.

Summary

  • Published package version: 1.0.34 (package.json updated from dev suffix to stable)
  • Dev dependency @fjell/eslint-config bumped to ^1.1.21 (patch update)
  • React and react-dom aligned to patch ^19.1.1 where present
  • CI test workflow limited to main and feature branches to reduce unnecessary test runs
  • Multiple package.json end-of-file (EOF) / newline normalizations applied

New Features

No user-facing product features were added in this release. Changes are focused on developer tooling, CI, and packaging.

Improvements

  • Dev dependency: @fjell/eslint-config -> ^1.1.21

    • Updated devDependency to pick up recent lint rule fixes/patches. This affects local linting runs and CI lint jobs that use devDependencies.
    • Impact: projects that rely on this shared eslint-config may see new or adjusted linting behavior; run linters and update lockfiles accordingly.

  • React alignment to latest patch (where present)

    • Bumped react and react-dom from ^19.1.0 -> ^19.1.1 in dependencies and peerDependencies in previous commits leading up to this release.
    • Impact: dependency ranges now permit the 19.1.1 patch. Consumers installing this package will get installations compatible with 19.1.1 when package managers resolve peers.

  • Versioning workflow and packaging preparation

    • package.json version progressed through development bumps (e.g., 1.0.33 -> 1.0.34-dev.0) and finalized to 1.0.34 for this stable release.
    • The release commit removes the dev suffix and prepares package.json for publishing.
    • Impact: published package metadata now reflects the stable release version.

Bug Fixes and Housekeeping

  • package.json EOF normalization and whitespace fixes

    • Several commits normalize end-of-file newlines and tidy whitespace in package.json. These changes are cosmetic but reduce spurious diffs in future edits and ensure consistent formatting across tools.
    • Impact: no functional change; reduces noisy diffs and potential tooling warnings.

  • CI workflow: limit test runs to main and feature branches

    • .github/workflows/test.yml was updated to remove release/** and working from the on.push.branches list.
    • YAML formatting was tidied (removed stray blank lines around setup steps) without changing runtime steps or the Node.js version used by the workflow.
    • Impact: pushes to branches matching release/** and the working branch will no longer trigger the test workflow. This reduces CI usage for ephemeral/release branches and focuses CI runs on main and feature branches. Review CI expectations if you depend on test runs on release/** or working branches.

Developer Experience

  • Linting behavior may change slightly due to the @fjell/eslint-config patch bump. Developers should:

    • Run the project's linting locally after updating node_modules/lockfile
    • Update lockfiles (package-lock.json / yarn.lock / pnpm-lock.yaml) to persist the new devDependency range

  • CI expectations

    • Developers creating temporary release branches or using a working branch should be aware that the test workflow will not run on those branches by default anymore. If tests are required for those branches, consider adding workflow dispatch triggers or adjusting branch patterns in the workflow.

Breaking Changes

  • No runtime API breaking changes were introduced. The release contains dependency and CI workflow changes that may affect development and CI behavior but not the published module's runtime interface.

Recommended Actions for Consumers and Maintainers

  • Update local install state and lockfiles after pulling this release to ensure the new devDependency versions are used.
  • Re-run linters and fix/accept any new lint findings resulting from the eslint-config bump.
  • Review CI usage patterns if tests were expected to run on release/** or working branches; update workflows if that behavior is still desired.
  • If relying on a specific React patch, confirm that package resolution gives the expected react/react-dom version now that ranges include ^19.1.1.

Notable Commits (high level)

  • Bump package version to 1.0.34 for release (finalize stable version)
  • Bump @fjell/eslint-config to patch release and normalize package.json EOF
  • Limit CI test workflow to main and feature branches; tidy YAML formatting
  • Bumped react/react-dom patch versions in prior development commits

Files/Areas Changed

  • package.json

    • version field updated to 1.0.34
    • devDependency @fjell/eslint-config updated to ^1.1.21
    • EOF/newline formatting normalized in multiple commits
    • previous intermediate dev version bumps (e.g. 1.0.34-dev.0) appeared during the release process

  • .github/workflows/test.yml

    • Reduced on.push.branches to only main and feature branches (removed release/** and working)
    • Minor YAML formatting cleanup

If additional detail is required (for example, exact lint rule changes introduced by the @fjell/eslint-config ^1.1.21 patch), consult the eslint-config changelog or the corresponding package release notes for that dependency.

Assets 2
Loading