@bananapus/omnichain-deployers-v6 0.0.46 → 0.0.47

package/package.json

@@ -1,18 +1,16 @@
 {
   "name": "@bananapus/omnichain-deployers-v6",
-  "version": "0.0.46",
+  "version": "0.0.47",
   "license": "MIT",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/Bananapus/nana-omnichain-deployers-v6"
   },
   "files": [
-    "CHANGELOG.md",
     "foundry.toml",
     "references/",
     "remappings.txt",
-    "script/Deploy.s.sol",
-    "script/helpers/",
+    "script/",
     "src/"
   ],
   "engines": {

package/CHANGELOG.md

@@ -1,76 +0,0 @@
-# Changelog
-
-## 0.0.43 — Bump v6 deps to nana-core-v6 0.0.53 cohort
-
-- `@bananapus/core-v6`: `^0.0.48 → ^0.0.53` ([PR #145](https://github.com/Bananapus/nana-core-v6/pull/145) — drops `via_ir` requirement on `JBCashOutHookSpecsLib`; new `pauseCrossProjectFeeFreeInflows` ruleset metadata flag for cross-project cashout opt-out).
-- `@bananapus/721-hook-v6`: `^0.0.47 → ^0.0.50`.
-- `@bananapus/suckers-v6`: `^0.0.37 → ^0.0.46`.
-- `@bananapus/buyback-hook-v6`: `^0.0.39 → ^0.0.46`.
-- `@bananapus/permission-ids-v6`: `^0.0.23 → ^0.0.25` (new `SET_SUCKER_PEER` permission referenced by suckers 0.0.46).
-- `JBBuybackHook` constructor signature changed in 0.0.45 (V4 PoolManager + Hooks moved to a one-shot setter). Updated `OmnichainForkTestBase` to construct then call `setChainSpecificConstants`.
-- All `JBRulesetMetadata` test literals patched to include `pauseCrossProjectFeeFreeInflows: false`. `JBBeforeCashOutRecordedContext` literals are unchanged (no new fields).
-
-## v6 carry-forward hook fix
-
-- **Carry-forward hook selection improved.** `queueRulesetsOf` now checks `latestQueuedOf(projectId)` before falling back to `currentOf(projectId)` when carrying forward a 721 hook. Previously it only read `currentOf`, which could miss a recently queued (and approved) ruleset's hook config. The source ruleset must have approval status `Approved` or `Empty` and a stored hook config in the deployer.
-- The `useDataHookForCashOut` flag is preserved from whichever source ruleset is selected during carry-forward.
-
-## Scope
-
-This file describes the verified change from `nana-omnichain-deployers-v5` to the current `nana-omnichain-deployers-v6` repo.
-
-## Current v6 surface
-
-- `JBOmnichainDeployer`
-- `IJBOmnichainDeployer`
-- `JBDeployerHookConfig`
-- `JBOmnichain721Config`
-- `JBTiered721HookConfig`
-
-## Summary
-
-- The deployer now assumes a 721 hook is part of the standard deployment path instead of a special-case path.
-- Hook composition is more explicit. The current repo separates 721-hook behavior from extra data-hook behavior and combines them deliberately.
-- The v6 test suite includes dedicated coverage for ownership transfer, controller validation, empty ruleset edge cases, hook composition, and invariants that were not present in the small v5 tree.
-- The repo moved to the v6 Solidity and dependency baseline.
-
-## Verified deltas
-
-- `launch721ProjectFor(...)`, `launch721RulesetsFor(...)`, and `queue721RulesetsOf(...)` no longer define the public API shape.
-- Their role is covered by overloaded `launchProjectFor(...)`, `launchRulesetsFor(...)`, and `queueRulesetsOf(...)` entry points that accept `JBOmnichain721Config`.
-- `extraDataHookOf(...)` and `tiered721HookOf(...)` replace the older single `dataHookOf(...)` view model.
-- The overloaded launch and queue functions now return the `IJB721TiersHook` they deploy or carry forward.
-
-## Breaking ABI changes
-
-- The 721-specific launch and queue entry points were removed from the public API shape.
-- `dataHookOf(...)` was replaced by `extraDataHookOf(...)` plus `tiered721HookOf(...)`.
-- `launchProjectFor(...)`, `launchRulesetsFor(...)`, and `queueRulesetsOf(...)` now have overloads that return the hook.
-- `JBOmnichain721Config` replaces the old direct 721 deploy config entrypoint model.
-
-## Indexer impact
-
-- Hook composition is now split across two tracked hook sources instead of one.
-- Launch and queue flows should expect a 721 hook in the returned state and in the deployer's stored per-ruleset data.
-
-## Migration notes
-
-- Update any code that expected separate "with 721" and "without 721" deployment paths to behave like v5.
-- Re-check ownership assumptions after hook deployment. The current repo is stricter and more explicit about that flow.
-- If you decode launch or queue inputs, use the current v6 structs instead of v5 layouts.
-
-## ABI appendix
-
-- Removed public API shape
-  - `launch721ProjectFor(...)`
-  - `launch721RulesetsFor(...)`
-  - `queue721RulesetsOf(...)`
-- Replaced with overload families
-  - `launchProjectFor(...)`
-  - `launchRulesetsFor(...)`
-  - `queueRulesetsOf(...)`
-- Replaced hook lookup model
-  - `dataHookOf(...)` -> `extraDataHookOf(...)` + `tiered721HookOf(...)`
-- New migration-sensitive structs
-  - `JBOmnichain721Config`
-  - `JBTiered721HookConfig`