Skip to content

chore: bump package version to 0.2.1 - #9

Merged
Bre77 merged 1 commit into
mainfrom
fm/tsfa-publish-021
Aug 1, 2026
Merged

chore: bump package version to 0.2.1#9
Bre77 merged 1 commit into
mainfrom
fm/tsfa-publish-021

Conversation

@Bre77

@Bre77 Bre77 commented Aug 1, 2026

Copy link
Copy Markdown
Member

Intent

Bump tesla-fleet-api from 0.2.0 to 0.2.1 so the already-merged src/tariff.ts / getTariffPeriods tariff resolver actually ships on npm. Verified via npm view that the currently-published 0.2.0 predates tariff.ts (published at an older gitHead, before the tariff resolver was added), even though it's on main and already exported from src/index.ts. Confirmed via local pnpm install/build + npm pack that the 0.2.1 tarball contains dist/tariff.js, dist/tariff.d.ts, dist/types/site_info.*, and src/tariff.ts, with getTariffPeriods correctly re-exported from dist/index.js, and all 90 vitest tests pass. Also added a short AGENTS.md note documenting that this repo has no CI publish workflow (a publish.yaml that ran npm publish on GitHub Release was added in 2024 and later deleted) - only ci.yml (typecheck+test) remains - so publishing 0.2.1 to npm after this PR merges will require a separate manual npm publish by someone with registry credentials, which is intentionally out of scope for this PR. This is a pure version-bump + doc-note change, no functional code changes.

What Changed

  • Bump the tesla-fleet-api package version from 0.2.0 to 0.2.1 for the tariff resolver release.
  • Document that npm publishing is manual because the repository has no publish workflow.

Risk Assessment

✅ Low: The change is limited to the intended 0.2.1 version bump and an accurate publishing-process note, with no functional code changes or source-verifiable intent contradictions.

Testing

Verified the two-file commit scope, completed the frozen-lockfile build, passed the focused tariff tests, inspected the generated 0.2.1 package contents, and demonstrated an end-user tarball installation resolving an ALL_DAY tariff at 0.21 through the package’s root export; all checks passed and reviewer-visible evidence was captured.

  • Evidence: tesla-fleet-api 0.2.1 npm tarball (local file: /tmp/no-mistakes-evidence/01KYY2ST467DBN1BNBC66DAK1X/tesla-fleet-api-0.2.1.tgz)
Evidence: Consumer installation and tariff resolution

{ "installedVersion": "0.2.1", "rootExportType": "function", "resolvedBuyRate": 0.21, "resolvedPeriod": "ALL_DAY" }

{
  "installedVersion": "0.2.1",
  "rootExportType": "function",
  "resolvedBuyRate": 0.21,
  "resolvedPeriod": "ALL_DAY"
}

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

✅ **Test** - passed

✅ No issues found.

  • git diff --name-status 78f36b7dcd050d04e2841f1e2891026f813d02e2 ff03abc92017738afd225c6b96397f65b8edb496
  • Inspected package.json, .github/workflows, src/index.ts, and targeted tariff tests
  • pnpm install --frozen-lockfile (including the prepare TypeScript build)
  • pnpm exec vitest run test/tariff.test.ts
  • pnpm pack --pack-destination /tmp/no-mistakes-evidence/01KYY2ST467DBN1BNBC66DAK1X
  • Installed the generated tarball into a temporary consumer project and invoked getTariffPeriods from the package root
  • Removed the temporary consumer project and confirmed the worktree remained clean
✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

npm's published 0.2.0 predates the tariff resolver (gitHead c839bb7,
before src/tariff.ts existed) even though it's on main and exported
from src/index.ts. This bump lets a real release ship getTariffPeriods.
@Bre77
Bre77 merged commit d21d4d1 into main Aug 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant