@perspectivefi/addresses 0.1.2 → 0.1.3

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/README.md CHANGED
@@ -175,7 +175,14 @@ rules: {
175
175
 
176
176
  ## Slack announcements
177
177
 
178
- After each successful publish, the workflow posts the registry changes to Slack (#nt-deployment-addresses-announcements): new addresses grouped by chain and domain (with the chain's DAO Safe as admin), address changes, status changes and removals. Changes to tags, notes, source or audit only are not announced, and nothing is posted when nothing relevant changed. If more than 50 addresses are added at once, only a per-chain count is posted. Messages stay under about 3500 characters and are split between chains when needed.
178
+ After each successful publish, the workflow posts the registry changes to Slack (#nt-deployment-addresses-announcements), most important first:
179
+
180
+ 1. **✅ Approved for prod**: entries whose status changed to `safe` (or that were added as `safe`), with the entry's `approval` reason (string, or `approval.basis`) when it has one.
181
+ 2. **⛔ Blocked**: status changes to `blocked` and additions that are `blocked` (these are not repeated under the additions).
182
+ 3. New addresses grouped by chain and domain.
183
+ 4. Address changes, other status changes, and removals.
184
+
185
+ Changes to tags, notes, source or audit only are not announced, and nothing is posted when nothing relevant changed. Large changes are summarised as one line per chain and domain (`ETHEREUM · Legacy 29`) plus a link to the full list: more than 50 additions, or more than 20 removals. Messages stay under about 3500 characters and are split between blocks when needed.
179
186
 
180
187
  Setup: a Slack admin creates an incoming webhook for the channel, and it is stored as the repository secret `SLACK_ADDRESSES_WEBHOOK_URL`. If the secret is missing or Slack is down, the step prints a `::warning::` and the publish still succeeds.
181
188
 
package/dist/cli.js CHANGED
@@ -22,7 +22,7 @@ var BUILTIN_ALLOW = [
22
22
  ];
23
23
  var DEFAULT_REGISTRY_URL = "https://cdn.jsdelivr.net/npm/@perspectivefi/addresses@latest/dist/registry.json";
24
24
  var FETCH_TIMEOUT_MS = 1e4;
25
- var BUNDLED_VERSION = true ? "0.1.2" : "dev";
25
+ var BUNDLED_VERSION = true ? "0.1.3" : "dev";
26
26
  var USAGE = `Usage: spectra-addresses check <paths...> [--mode warn|enforce] [--allow <json file>]... [--registry <url|file>] [--offline]
27
27
 
28
28
  --mode warn (default) or enforce. Falls back to env ADDRESS_GATE.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@perspectivefi/addresses",
3
- "version": "0.1.2",
3
+ "version": "0.1.3",
4
4
  "description": "Contract address registry for Spectra: one list of every address, each with a status. Prod only accepts `safe`.",
5
5
  "main": "./dist/index.js",
6
6
  "module": "./dist/index.mjs",