Promote @eldrforge/shared to v0.1.1 — remove prerelease suffix

Overview

This release updates package metadata to a canonical semver release by removing the prerelease suffix from package.json. The only functional edit in this change is the version field: it was changed from 0.1.1-dev.1 to 0.1.1 (commit 2b861c8). The change is explicitly limited to package metadata and is intended to prepare the package for publishing and for consumers that expect a non-prerelease version identifier.

What changed

• Updated package version in package.json from 0.1.1-dev.1 → 0.1.1 (commit 2b861c8). This removes the prerelease identifier and promotes the package to a canonical semver release.
• Left runtime-related metadata unchanged: the commit notes that name, description, main, and type remain the same, so the runtime entrypoint and module type are preserved. No code, entrypoint, or module-format changes were made.
• The commit message makes the semantic effect explicit: a normal 0.1.1 release now takes precedence over any 0.1.1-* prerelease tags when resolved by package managers. This is a packaging/semver metadata change rather than a behavioral or API change.

Why this was done (implications)

• Preparing for publish: removing the prerelease suffix makes this metadata suitable for publishing as a stable release and for consumers/tools that expect a non-prerelease version string (the commit message states this intent).
• Dependency resolution: because 0.1.1 is the canonical release, package managers that select versions by semver precedence will prefer 0.1.1 over prerelease variants like 0.1.1-dev.1 when ranges allow it. That changes how version selection behaves only in cases where ranges are permissive; it does not modify the package contents.
• No runtime/API impact: since main and type were not changed, this release should not affect runtime behavior or module resolution for dependent projects.

Impact and recommended actions

• For consumers: no code changes are required. If a project depends on a loose semver range (for example ^0.1.0 or >=0.1.0), that range may now resolve to the canonical 0.1.1 release instead of a prior prerelease. If a project explicitly pinned to 0.1.1-dev.1, that exact pin remains valid until the dependency is updated.
• For maintainers: this metadata change prepares the package for publishing. If the intention is to publish this version, run the normal publish process after verifying registry settings and any CI/publishing workflow that depends on a non-prerelease version.

Files changed (single metadata edit)

• package.json

Before / After (version field)

// before
"version": "0.1.1-dev.1"

// after
"version": "0.1.1"

Trace

• Commit: 2b861c8 — "Promote package to release version by removing prerelease suffix" (updates package.json).