automategraph 1.5.0 → 1.5.2
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/CHANGELOG.md +8 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,14 @@
|
|
|
3
3
|
All notable changes to the AutomateGraph Execution Engine.
|
|
4
4
|
Format follows [Keep a Changelog](https://keepachangelog.com/); the project uses semver.
|
|
5
5
|
|
|
6
|
+
## [1.5.2] — First registry publish
|
|
7
|
+
|
|
8
|
+
No code changes. The 1.5.0 and 1.5.1 uploads were accepted by the registry but held by the
|
|
9
|
+
account's publish policy — bypass-2FA granular tokens are being restricted for direct
|
|
10
|
+
publishing (see https://gh.io/npm-gat-bypass2fa-deprecation), and a directly submitted version
|
|
11
|
+
can no longer be staged either, so those two numbers are consumed. 1.5.2 carries the identical
|
|
12
|
+
tarball through the supported path: `npm stage publish` + approval.
|
|
13
|
+
|
|
6
14
|
## [1.5.0] — Script loading
|
|
7
15
|
|
|
8
16
|
A document can now say where its functions live and have them loaded: `scripts` entries point at
|