tibber-aws 7.0.22 → 7.0.24
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +9 -6
- package/readme.md +38 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "tibber-aws",
|
|
3
|
-
"version": "7.0.
|
|
3
|
+
"version": "7.0.24",
|
|
4
4
|
"description": "",
|
|
5
5
|
"main": "./dist/src/index.js",
|
|
6
6
|
"scripts": {
|
|
@@ -28,14 +28,12 @@
|
|
|
28
28
|
"author": "tibber",
|
|
29
29
|
"license": "ISC",
|
|
30
30
|
"devDependencies": {
|
|
31
|
-
"@semantic-release/changelog": "^6.0.3",
|
|
32
|
-
"@semantic-release/git": "^10.0.0",
|
|
33
31
|
"@types/jest": "^29.5.8",
|
|
34
32
|
"@types/jszip": "^3.4.1",
|
|
35
|
-
"@types/node": "20.19.
|
|
33
|
+
"@types/node": "20.19.43",
|
|
36
34
|
"@types/randomstring": "^1.1.11",
|
|
37
35
|
"dotenv-cli": "^4.0.0",
|
|
38
|
-
"glob": "^
|
|
36
|
+
"glob": "^13.0.0",
|
|
39
37
|
"gts": "7.0.0",
|
|
40
38
|
"husky": "^8.0.3",
|
|
41
39
|
"jest": "^30.3.0",
|
|
@@ -53,7 +51,12 @@
|
|
|
53
51
|
"resolutions": {
|
|
54
52
|
"undici": "^7.24.4",
|
|
55
53
|
"flatted": "^3.4.0",
|
|
56
|
-
"fast-xml-parser": "~5.
|
|
54
|
+
"fast-xml-parser": "~5.10.0",
|
|
55
|
+
"picomatch": "4.0.5",
|
|
56
|
+
"yaml": "2.9.0",
|
|
57
|
+
"**/libnpmdiff/diff": "8.0.4",
|
|
58
|
+
"**/ts-node/diff": "4.0.4",
|
|
59
|
+
"tmp": "0.2.7"
|
|
57
60
|
},
|
|
58
61
|
"dependencies": {
|
|
59
62
|
"@aws-sdk/client-lambda": "^3.1013.0",
|
package/readme.md
CHANGED
|
@@ -1,6 +1,44 @@
|
|
|
1
1
|
# tibber-aws
|
|
2
2
|
Thie repo is a typescript wrapper around the AWS SDK for Javascript.
|
|
3
3
|
|
|
4
|
+
## Releases & publishing — read before merging a PR
|
|
5
|
+
|
|
6
|
+
Merging to `master` runs the CircleCI `build_and_deploy` workflow. The
|
|
7
|
+
`deploy` job runs [semantic-release](https://semantic-release.gitbook.io/),
|
|
8
|
+
and **the squash-commit title decides whether a new version is published**
|
|
9
|
+
(default conventional-commit rules):
|
|
10
|
+
|
|
11
|
+
| Squash title | Result |
|
|
12
|
+
|---|---|
|
|
13
|
+
| `fix: …` / `fix(deps): …` | patch release |
|
|
14
|
+
| `feat: …` | minor release |
|
|
15
|
+
| `feat!: …` or a `BREAKING CHANGE:` footer | major release |
|
|
16
|
+
| `chore: …`, `docs: …`, `refactor: …`, or a plain title (e.g. Renovate's default `Update dependency x to vY`) | **no release** — the merge ships nothing to npm |
|
|
17
|
+
|
|
18
|
+
**Merging a dep-update PR (Renovate/Dependabot)?** The default squash title
|
|
19
|
+
does *not* publish. If consumers should get the bump (security fixes
|
|
20
|
+
especially), edit the squash title to `fix(deps): …` in the merge dialog.
|
|
21
|
+
Note: a later release publishes whatever is on `master` at that point, so
|
|
22
|
+
unreleased chore-merges still ship with the next `fix`/`feat` release.
|
|
23
|
+
|
|
24
|
+
**Versioning is tag-based.** The git tag, GitHub release (with generated
|
|
25
|
+
notes), and npm carry the real version — the in-repo `package.json` version
|
|
26
|
+
and `CHANGELOG.md` are frozen at v7.0.23 and no release commit is pushed
|
|
27
|
+
back to `master` (its branch rules forbid it).
|
|
28
|
+
|
|
29
|
+
**Publishing uses npm [trusted publishing](https://docs.npmjs.com/trusted-publishers)**
|
|
30
|
+
via CircleCI OIDC — there is no stored npm token. Requirements: the
|
|
31
|
+
npmjs.com trusted-publisher entry for this package (CircleCI, org `tibber`,
|
|
32
|
+
project `tibber-aws`, job `deploy`) and npm ≥ 11.11 in the job (the
|
|
33
|
+
`cimg/node:24` image). Provenance is attached automatically.
|
|
34
|
+
|
|
35
|
+
**If the deploy job fails after tagging** (e.g. a registry error), the tag
|
|
36
|
+
and GitHub release exist but npm doesn't have the version. A plain rerun
|
|
37
|
+
will no-op ("no new version to release"). Recovery: delete the tag
|
|
38
|
+
(`git push origin :refs/tags/vX.Y.Z`), delete the GitHub release if one was
|
|
39
|
+
created, then rerun the `deploy` job. A merge with no pending release logs
|
|
40
|
+
`already published, skipping` and exits green.
|
|
41
|
+
|
|
4
42
|
## Version 6.x.x changes
|
|
5
43
|
- Migrated to aws sdk 3.x
|
|
6
44
|
- Removed ECS Api
|