@networkpro/blog 1.2.7 → 1.3.4

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 CHANGED
@@ -16,6 +16,106 @@ formatting may vary.
16
16
 
17
17
  ---
18
18
 
19
+ ## [1.3.4] - 2025-06-23
20
+
21
+ ### Changed
22
+
23
+ - Bumped version to `v1.3.4`.
24
+
25
+ ### Fixed
26
+
27
+ - Removed legacy `.npmrc` file that was overriding registry authentication and
28
+ causing `401 Unauthorized` errors during publishing.
29
+ - Restored default registry handling through `setup-node` for reliable
30
+ token-based authentication to `npmjs.org`.
31
+
32
+ ---
33
+
34
+ ## [1.3.3] - 2025-06-23
35
+
36
+ ### Added
37
+
38
+ - Diagnostic logging to verify active registry, token configuration, and
39
+ `.npmrc` state prior to publishing.
40
+
41
+ ### Changed
42
+
43
+ - Bumped version to `v1.3.3`.
44
+
45
+ ### Fixed
46
+
47
+ - Resolved persistent authentication failure during publish by reintroducing
48
+ `npm ci` and upgrading npm in registry workflows.
49
+ - Adjusted step ordering to ensure environment and Git config are fully
50
+ initialized before registry checks.
51
+
52
+ ---
53
+
54
+ ## [1.3.2] - 2025-06-23
55
+
56
+ ### Added
57
+
58
+ - Authentication check (`npm whoami`) before publish to confirm registry access.
59
+
60
+ ### Changed
61
+
62
+ - Bumped version to `v1.3.2`.
63
+
64
+ ### Fixed
65
+
66
+ - Resolved publishing failure caused by missing lockfile and outdated npm
67
+ version in registry workflows.
68
+ - Reintroduced `npm ci` and upgraded npm to ensure compatibility with scoped
69
+ package publishing.
70
+
71
+ ---
72
+
73
+ ## [1.3.1]
74
+
75
+ ### Changes
76
+
77
+ - Removed `cache-dependency-path` from publish workflows to avoid
78
+ lockfile-related cache issues.
79
+ - Verified presence of `package-lock.json` in the extracted archive and
80
+ maintained default npm caching behavior.
81
+ - Bumped version to `v1.3.1`.
82
+
83
+ ---
84
+
85
+ ## [1.3.0]
86
+
87
+ ### Added
88
+
89
+ - Introduced a test publish workflow (`.github/workflows/publish-test.yml`) to
90
+ validate the `git archive` packaging method via dry-run publishing.
91
+
92
+ ### Changed
93
+
94
+ - Bumped version to `v1.3.0`.
95
+ - Reformatted `.github/COMMIT_GUIDE.md` to align with Prettier conventions.
96
+ - Refactored `.github/workflows/publish.yml` to use `git archive` for publishing
97
+ to registries.
98
+
99
+ ---
100
+
101
+ ## [1.2.8] - 2025-06-23
102
+
103
+ ### Added
104
+
105
+ - New blog post: `2025-06-23-encryption-eff.md` added to `/src/posts`.
106
+ - Included associated promotional images: `encryption-eff.png` and
107
+ `encryption-eff.webp`
108
+ - Introduced `.github/workflows/COMMIT_GUIDE.md` for reference when creating
109
+ commit messages
110
+
111
+ ### Changed
112
+
113
+ - Bumped version to `v1.2.8`.
114
+ - Upgraded `prettier` from `3.5.3` to `3.6.0`.
115
+ - Upgraded `stylelint` from `^16.20.0` to `^16.21.0`.
116
+
117
+ ---
118
+
19
119
  ## [1.2.7] - 2025-06-16
20
120
 
21
121
  ### Added
@@ -44,5 +144,10 @@ formatting may vary.
44
144
 
45
145
  <!-- Link references -->
46
146
 
47
- [Unreleased]: https://github.com/netwk-pro/blog/compare/v1.2.7...HEAD
147
+ [Unreleased]: https://github.com/netwk-pro/blog/compare/v1.3.3...HEAD
148
+ [1.3.3]: https://github.com/netwk-pro/blog/releases/tag/v1.3.3
149
+ [1.3.2]: https://github.com/netwk-pro/blog/releases/tag/v1.3.2
150
+ [1.3.1]: https://github.com/netwk-pro/blog/releases/tag/v1.3.1
151
+ [1.3.0]: https://github.com/netwk-pro/blog/releases/tag/v1.3.0
152
+ [1.2.8]: https://github.com/netwk-pro/blog/releases/tag/v1.2.8
48
153
  [1.2.7]: https://github.com/netwk-pro/blog/releases/tag/v1.2.7
File without changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@networkpro/blog",
3
- "version": "1.2.7",
3
+ "version": "1.3.4",
4
4
  "description": "The official blog of Network Pro Strategies (Network Pro™).",
5
5
  "keywords": [
6
6
  "advisory",
@@ -59,8 +59,8 @@
59
59
  "markdownlint": "^0.38.0",
60
60
  "markdownlint-cli2": "^0.18.1",
61
61
  "postcss": "^8.5.6",
62
- "prettier": "3.5.3",
63
- "stylelint": "^16.20.0",
62
+ "prettier": "3.6.0",
63
+ "stylelint": "^16.21.0",
64
64
  "stylelint-config-html": "^1.1.0",
65
65
  "stylelint-config-recommended": "^16.0.0",
66
66
  "stylelint-order": "^7.0.0"
@@ -0,0 +1,11 @@
1
+ authors:
2
+ team:
3
+ name: Network Pro
4
+ description: Creator
5
+ avatar: https://avatars.githubusercontent.com/u/170266279
6
+ url: https://netwk.pro/
7
+ SunDevil311:
8
+ name: Scott Lopez
9
+ description: Creator
10
+ avatar: https://avatars.githubusercontent.com/u/10506001
11
+ url: https://github.com/SunDevil311
Binary file
Binary file
@@ -0,0 +1,57 @@
1
+ ---
2
+ date:
3
+ created: 2025-06-23
4
+ title: 'Encryption is not a loophole'
5
+ summary:
6
+ Encryption is not a loophole. It's a lifeline. Act now to protect encryption!
7
+ authors:
8
+ - team
9
+ categories:
10
+ - Privacy
11
+ - Security
12
+ - Policy
13
+ tags:
14
+ - privacy
15
+ - security
16
+ - cybersecurity
17
+ - encryption
18
+ - eff
19
+ - policy
20
+ ---
21
+
22
+ # 🔐 Encryption is not a loophole
23
+
24
+ ## It’s a lifeline
25
+
26
+ Right now, Congress is considering legislation that could **effectively ban
27
+ encrypted apps** by forcing companies to build dangerous backdoors into private
28
+ communications.
29
+
30
+ These proposals threaten the security of journalists, whistleblowers, business
31
+ professionals, and everyday users who depend on end-to-end encryption to
32
+ communicate safely and confidentially. 💼🛡️
33
+
34
+ **EFF is sounding the alarm. And we all should be too.**
35
+
36
+ <!-- more -->
37
+
38
+ 📣 This isn’t just a tech issue—it’s a fundamental human rights issue. Weakening
39
+ encryption undermines trust in our digital infrastructure, increases
40
+ vulnerability to cyber threats, and sets a dangerous precedent for global
41
+ privacy standards.
42
+
43
+ It’s time to act. Contact your representatives and demand they protect encrypted
44
+ communications and uphold digital rights.
45
+
46
+ 👉 Take action now:
47
+ [act.eff.org/action/tell-congress-don-t-outlaw-encrypted-applications](https://act.eff.org/action/tell-congress-don-t-outlaw-encrypted-applications)
48
+
49
+ &nbsp;
50
+
51
+ <figure class="poster-figure">
52
+ <source srcset="/img/encryption-eff.webp" type="image/webp" />
53
+ <img src="/img/encryption-eff.png" alt="Encryption is not a loophole. It's a lifeline." style="width: 60%; height: 60%;">
54
+ <figcaption>Encryption is not a loophole – featured visual</figcaption>
55
+ </figure>
56
+
57
+ <!-- cspell:ignore backdoors whistleblowers -->
@@ -0,0 +1 @@
1
+ draft: true