@bananapus/ownable-v6 0.0.27 → 0.0.29
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 +3 -5
- package/CHANGELOG.md +0 -39
- package/foundry.lock +0 -5
package/package.json
CHANGED
|
@@ -1,14 +1,12 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@bananapus/ownable-v6",
|
|
3
|
-
"version": "0.0.
|
|
3
|
+
"version": "0.0.29",
|
|
4
4
|
"license": "MIT",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
7
7
|
"url": "git+https://github.com/Bananapus/nana-ownable-v6"
|
|
8
8
|
},
|
|
9
9
|
"files": [
|
|
10
|
-
"CHANGELOG.md",
|
|
11
|
-
"foundry.lock",
|
|
12
10
|
"foundry.toml",
|
|
13
11
|
"references/",
|
|
14
12
|
"remappings.txt",
|
|
@@ -19,8 +17,8 @@
|
|
|
19
17
|
"node": ">=20.0.0"
|
|
20
18
|
},
|
|
21
19
|
"dependencies": {
|
|
22
|
-
"@bananapus/core-v6": "^0.0.
|
|
23
|
-
"@bananapus/permission-ids-v6": "^0.0.
|
|
20
|
+
"@bananapus/core-v6": "^0.0.60",
|
|
21
|
+
"@bananapus/permission-ids-v6": "^0.0.27",
|
|
24
22
|
"@openzeppelin/contracts": "5.6.1"
|
|
25
23
|
},
|
|
26
24
|
"scripts": {
|
package/CHANGELOG.md
DELETED
|
@@ -1,39 +0,0 @@
|
|
|
1
|
-
# Changelog
|
|
2
|
-
|
|
3
|
-
## Scope
|
|
4
|
-
|
|
5
|
-
This file describes the verified change from `nana-ownable-v5` to the current `nana-ownable-v6` repo.
|
|
6
|
-
|
|
7
|
-
## Current v6 surface
|
|
8
|
-
|
|
9
|
-
- `JBOwnable`
|
|
10
|
-
- `JBOwnableOverrides`
|
|
11
|
-
- `IJBOwnable`
|
|
12
|
-
- `JBOwner`
|
|
13
|
-
|
|
14
|
-
## Summary
|
|
15
|
-
|
|
16
|
-
- Project-backed ownership is more defensive than in v5. The current implementation tolerates invalid or burned project NFTs by handling `ownerOf` failures instead of surfacing them as unchecked behavior.
|
|
17
|
-
- The project-ownership path validates its inputs more strictly before transferring control to a project.
|
|
18
|
-
- The implementation files now compile on the v6 `0.8.28` baseline instead of the old floating `^0.8.23` setup.
|
|
19
|
-
|
|
20
|
-
## Verified deltas
|
|
21
|
-
|
|
22
|
-
- `JBOwnable` now emits ownership-transfer events through `_msgSender()` instead of raw `msg.sender`.
|
|
23
|
-
- The transfer-event path is explicitly documented to revert when the new project does not exist, instead of silently tolerating a bad target.
|
|
24
|
-
- The current imports point at `core-v6`, not `core-v5`.
|
|
25
|
-
|
|
26
|
-
## Breaking ABI changes
|
|
27
|
-
|
|
28
|
-
- There is no meaningful public function migration in `IJBOwnable`; the interface mostly preserved its shape.
|
|
29
|
-
- The important migration is behavioral: project-backed ownership resolution and transfer validation are stricter.
|
|
30
|
-
|
|
31
|
-
## Indexer impact
|
|
32
|
-
|
|
33
|
-
- Event names are stable, but the `caller` field is now emitted through `_msgSender()` semantics in the implementation.
|
|
34
|
-
- Meta-transaction-aware consumers should prefer the v6 behavior over raw-`msg.sender` assumptions.
|
|
35
|
-
|
|
36
|
-
## Migration notes
|
|
37
|
-
|
|
38
|
-
- If you depended on `owner()` reverting for invalid project-backed ownership states, revisit that expectation.
|
|
39
|
-
- Rebuild imports against the v6 core package and the current ownable contracts. This repo is small, but the behavior is intentionally stricter than v5.
|