Repository navigation
chore: prepare TypeScript client 2.0.0 - #4
Merged
Merged
Conversation
Use a major version for the changed CSV default, document migration and pin contracts to the released Python 3.0.0 commit.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Prepare @energy-tracker/api-client 2.0.0 for publication. The merged CSV change alters the default delimiter from comma to semicolon, so existing consumers must opt in to the new major version.
Update package and lockfile versions, document
delimiter: CsvDelimiter.COMMAfor preserving 1.x output, shorten the default's API comment and pin unchanged shared contract files to the merged Python 3.0.0 release commit.Validation:
npm run checkpasses with 158 tests, type checking, formatting, coverage and packed-package checks for CommonJS, ESM and TypeScript 5.8/7 consumers.npm run check:release -- v2.0.0passes.This PR is required before tagging: the release workflow checks both the version/tag match and that the release commit belongs to main. No tag or publication has been performed.