upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Dilger <mike@mikedilger.com>2024-02-16 14:15:32 +1300
committerGitHub <noreply@github.com>2024-02-15 22:15:32 -0300
commit62c48eff58d6dd4d2b0a817bbb36cd75087f0ae3 (patch)
treef4c9b4c696d2bdef45a1e0774156fa7dc298e7f5
parentcbec02ab52ffb062f7b7712e0ed6ec524cfe0b6a (diff)
Breaking changes list (#1052)
* Start of new BREAKING.md changes list * more * Make NIP column into links * notes * Make commits links * Remove optional P tag entry, was not breaking * Update BREAKING with nip-49 breaking change
-rw-r--r--BREAKING.md21
-rw-r--r--README.md5
2 files changed, 26 insertions, 0 deletions
diff --git a/BREAKING.md b/BREAKING.md
new file mode 100644
index 0000000..2a85a28
--- /dev/null
+++ b/BREAKING.md
@@ -0,0 +1,21 @@
1# Breaking Changes
2
3This is a history of NIP changes that potentially break pre-existing implementations, in
4reverse chronological order.
5
6| Date | Commit | NIP | Change |
7| ----------- | --------- | -------- | ------ |
8| 2024-02-16 | [cbec02ab](https://github.com/nostr-protocol/nips/commit/cbec02ab) | [NIP-49](49.md) | Password first normalized to NFKC |
9| 2024-02-15 | [afbb8dd0](https://github.com/nostr-protocol/nips/commit/afbb8dd0) | [NIP-39](39.md) | PGP identity was removed |
10| 2024-02-07 | [d3dad114](https://github.com/nostr-protocol/nips/commit/d3dad114) | [NIP-46](46.md) | Connection token format was changed |
11| 2024-01-30 | [1a2b21b6](https://github.com/nostr-protocol/nips/commit/1a2b21b6) | [NIP-59](59.md) | 'p' tag became optional |
12| 2023-01-27 | [c2f34817](https://github.com/nostr-protocol/nips/commit/c2f34817) | [NIP-47](47.md) | optional expiration tag should be honored |
13| 2024-01-10 | [3d8652ea](https://github.com/nostr-protocol/nips/commit/3d8652ea) | [NIP-02](02.md) | list entries should be chronological |
14| 2024-01-10 | [3d8652ea](https://github.com/nostr-protocol/nips/commit/3d8652ea) | [NIP-51](51.md) | list entries should be chronological |
15
16Breaking changes prior to 2024-01-01 are not yet documented.
17
18## NOTES
19
20- If it isn't clear that a change is breaking or not, we list it.
21- The date is the date it was merged, not necessarily the date of the commit.
diff --git a/README.md b/README.md
index caecc01..b9ca8aa 100644
--- a/README.md
+++ b/README.md
@@ -15,6 +15,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/nos
15- [Criteria for acceptance of NIPs](#criteria-for-acceptance-of-nips) 15- [Criteria for acceptance of NIPs](#criteria-for-acceptance-of-nips)
16- [Is this repository a centralizing factor?](#is-this-repository-a-centralizing-factor) 16- [Is this repository a centralizing factor?](#is-this-repository-a-centralizing-factor)
17- [How this repository works](#how-this-repository-works) 17- [How this repository works](#how-this-repository-works)
18- [Breaking Changes](#breaking-changes)
18- [License](#license) 19- [License](#license)
19 20
20--- 21---
@@ -261,6 +262,10 @@ Standards may emerge in two ways: the first way is that someone starts doing som
261 262
262These two ways of standardizing things are supported by this repository. Although the second is preferred, an effort will be made to codify standards emerged outside this repository into NIPs that can be later referenced and easily understood and implemented by others -- but obviously as in any human system discretion may be applied when standards are considered harmful. 263These two ways of standardizing things are supported by this repository. Although the second is preferred, an effort will be made to codify standards emerged outside this repository into NIPs that can be later referenced and easily understood and implemented by others -- but obviously as in any human system discretion may be applied when standards are considered harmful.
263 264
265## Breaking Changes
266
267[Breaking Changes](BREAKING.md)
268
264## License 269## License
265 270
266All NIPs are public domain. 271All NIPs are public domain.