Replace prerelease version strings in package-lock.json with stable 0.1.14 * Update top-level "version" in package-lock.json from "0.1.14-dev.0" to "0.1.14" * Update packages[""].version entry in package-lock.json from "0.1.14-dev.0" to "0.1.14" *... #12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 14 commits
December 12, 2025 11:04
…d align tests
- Update tests/github.test.ts to stop asserting run() receives { cwd: undefined } or { suppressErrorLogging: true }; expectations now only verify the git command strings
- Remove test cases that verified cwd passthrough for GitHub.getCurrentBranchName, GitHub.getRepoDetails, and findOpenPullRequestByHeadRef, reflecting that callers no longer supply cwd
- Adjust open-PR lookup test to no longer expect getRepoDetails to invoke run() with cwd/suppressErrorLogging options
- Add .kodrdriv-test-cache.json as an empty object to reset the local test cache state
- src/github.ts updated accordingly (file changed), consistent with tests no longer depending on option forwarding behaviour
* Update dependency entry in package.json: "@eldrforge/git-tools" from "^0.1.9" to "^0.1.10" * Raises the minimum resolved version to 0.1.10 while keeping the caret range (>=0.1.10 <0.2.0), so package managers will choose 0.1.x releases at or above 0.1.10 * Changes dependency resolution baseline only — follow-up install will update the lockfile / node_modules to reflect the new minimum * Change is confined to package.json and does not alter source code or runtime imports (only the declared dependency version)
* Delete the "version" property from package.json (removed both "0.1.13-dev.0" and "0.1.13" lines) — change is confined to package.json * Leaves package metadata keys (description, main, type) intact; only the version field was removed * Practical effect: package.json no longer declares a package version — tooling or scripts that read package.json.version (publish steps, semver checks, changelog generators) will need an alternative source (git tags/CI-provided version or restored field) or may fail until a version is supplied
* Delete root-level "version" entry in package-lock.json * Remove the "version" key under packages[""] (the root package metadata) in package-lock.json * Leave other lockfile metadata intact (name, lockfileVersion, requires, license, dependencies remain as shown) * Technical effect: package-lock.json no longer exposes the package version at either the lockfile root or the packages[""] metadata; any tooling that reads package-lock.json.version will no longer find a value and must rely on other sources (lockfileVersion/package entries or external versioning) * Change is local to package-lock.json and does not modify other fields or dependency entries shown in the diff
* Update package.json: change dependencies["@eldrforge/git-tools"] from "^0.1.10" to "^0.1.11" * The caret range remains in place; npm will resolve versions >=0.1.11 and <0.2.0 (patch-level bump within the 0.1.x channel) * No other source files changed; the @octokit/rest entry in dependencies is unchanged * Operational note: lockfile (package-lock.json / yarn.lock) should be refreshed in CI or before release so installs reproduce the new resolved dependency version
* Update package.json: change "version" value from "0.1.14-dev.0" to "0.1.14" * Removes the pre-release suffix, promoting the package metadata to a stable semver release identifier * Affects how consumers, registries and publish tooling read the package identity (npm/semver will treat this as the final 0.1.14 release instead of a dev prerelease) * Change is limited to package.json and updates only the package metadata used for publishing and version checks
….1.14 * Update top-level "version" in package-lock.json from "0.1.14-dev.0" to "0.1.14" * Update packages[""].version entry in package-lock.json from "0.1.14-dev.0" to "0.1.14" * lockfileVersion (3) and dependency entries are unchanged; only the recorded package version metadata was adjusted * Effect: the lockfile now records the package as a stable semver release (no prerelease suffix), which affects how package identity is read by npm tooling and reproducible installs/publish metadata
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
ghost
merged commit
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Automated release PR.