ipor-fusion 4.0.0.dev139__tar.gz → 4.0.0.dev144__tar.gz

{ipor_fusion-4.0.0.dev139 → ipor_fusion-4.0.0.dev144}/AGENTS.md

@@ -141,11 +141,16 @@ the lifecycle matrix follows that.
   it is pinned exactly (`ipor-fusion==3.17.0.dev4`); pip also takes it when
   no stable release satisfies the specifier (`>=3.17` before 3.17.0). `fusion
   changelog` has no section for a dev version.
-- Release notes render only the commit subject; body prose is dropped. Two
-  footers survive: `BREAKING CHANGE: <what breaks, what to do instead>` is
-  required whenever the subject carries `!` (the `!` bumps the version but
-  renders nothing), and `NOTICE: <what the reader must do>` is for changes that
-  need action (a migration, a new env var or config key). Omit it otherwise.
+- Release notes (CHANGELOG.md and the GitHub release) render only commit
+  subjects. python-semantic-release's default template (10.5.3) shows the
+  `BREAKING CHANGE:` / `NOTICE:` footers of only the first commit per section,
+  so in practice they do not reach the notes. Still write them: a `!` subject
+  requires a `BREAKING CHANGE: <what breaks, what to do instead>` footer (the
+  `!` bumps the version), and `NOTICE: <what the reader must do>` marks changes
+  that need action (a migration, a new env var or config key); the release
+  author uses them to edit the GitHub release notes by hand after a release.
+  Anything a consumer must do also belongs in the migration guide or README,
+  which ship in the wheel.
 - No AI attribution trailers or "generated with" lines in commits or PRs.
 - Branch and open a PR; `main` only moves through PRs and the release workflow.
 - Dependencies: `>=x,<next-major` ranges in `pyproject.toml`, resolved by

{ipor_fusion-4.0.0.dev139 → ipor_fusion-4.0.0.dev144}/MIGRATION_4.md

@@ -6,10 +6,11 @@ the details, and each change is described once, in its section.
 
 ## Start here
 
-> **A 3.x program fails when a line runs, not when it is imported.**
-> `PlasmaVault(ctx, address)`, `ERC20(ctx, token)` or any other `Wrapper(ctx, ...)`
-> raises `TypeError` only when that line executes, and so does `call.call()` without
-> a context. A service that wraps its reads in a broad `except Exception` degrades
+> **Most 3.x calls fail only when the line runs.** A removed import
+> (`ipor_fusion.fuses.crosschain`, `NavMark`, the 3.x cache functions) fails at
+> import, but `PlasmaVault(ctx, address)`, `ERC20(ctx, token)` or any other
+> `Wrapper(ctx, ...)` raises `TypeError` only when that line executes, and so does
+> `call.call()` without a context. A service that wraps its reads in a broad `except Exception` degrades
 > silently (empty values, skipped vaults) instead of failing. Before you deploy:
 >
 > - search for wrappers built with a context (`(ctx,`, `(self.ctx,`, `(self._ctx,`)
@@ -189,8 +190,7 @@ The vault read is one pinned snapshot, and the chain is always the context's:
   no longer takes `resolve_symbol`. `metadata=True` names the ERC20 holdings in the
   result and its findings. `validate_vault_state(state)` is pure: a custom
   `VaultState` also provides `vault`, `chain_id`, `market_balances`, `erc20` and the
-  queue's `shares_to_release_assets`. `read_erc20_holdings` is gone: the holdings are
-  `VaultData.erc20`.
+  queue's `shares_to_release_assets`.
 - `build_vault_info_json(data, *, resolve_name=None)` renders from the snapshot and
   reads nothing; the chain and its label come from `data.chain_id`. Without
   `resolve_name` it names no contract (see
@@ -280,7 +280,8 @@ fails at run time:
   zero-address placeholder. `execute()` without `vault` and `alpha` raises
   `ValueError`, as does `execute_call` without `from_` or `alpha`.
 - `fetch_unpriceable_priced_tokens(ctx, *, price_oracle, underlying, balance_fuses,
-  market_substrates, morpho_positions)` takes everything after `ctx` by keyword.
+  market_substrates, morpho_positions)` takes everything after `ctx` by keyword, and
+  its `oracle_address` parameter is renamed `price_oracle`.
 - `get_contract_name(chain_id, address, *, api_key=None, cache=None)` and
   `get_deployment_tx(chain_id, address, *, api_key=None)` take `api_key` by keyword.
 - `build_morpho_blue_market_json(*, market_id, chain_id, params, state, rates,
@@ -346,9 +347,11 @@ is the wrong one.
 - The Morpho API client raises `MorphoApiError` for every answer it cannot use and
   every transport failure, never `KeyError`, `TypeError` or `ValueError`:
   - a required market id or address (market and V1 allocation ids, V1 flow-cap ids,
-    vault/asset/owner/token/oracle/IRM/allocator addresses) that is absent or
-    invalid; an optional address (curator, guardian, fee recipients, ...) that is
-    absent or `""` reads as `None`, and raises only when present and invalid;
+    vault/asset/owner/token/oracle/IRM addresses) that is absent or invalid; an
+    optional address (curator, guardian, fee recipients, ...) that is absent or `""`
+    reads as `None`, and raises only when present and invalid; an allocator or
+    sentinel entry without an address is skipped, and one with an invalid address
+    raises;
   - any other answer it cannot read (a missing key such as a `loanAsset` without
     `address`, a value of the wrong type, a body that is not a JSON object);
   - any `OSError` or `http.client.HTTPException` while fetching (it caught only

{ipor_fusion-4.0.0.dev139 → ipor_fusion-4.0.0.dev144}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: ipor-fusion
-Version: 4.0.0.dev139
+Version: 4.0.0.dev144
 Summary: The IPOR Fusion SDK for Python
 Project-URL: homepage, https://ipor.io
 Project-URL: repository, https://github.com/IPOR-Labs/ipor-fusion.py

{ipor_fusion-4.0.0.dev139 → ipor_fusion-4.0.0.dev144}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "ipor-fusion"
-version = "4.0.0.dev139"
+version = "4.0.0.dev144"
 description = "The IPOR Fusion SDK for Python"
 authors = [
     { name = "Adam Mydlarz", email = "amydlarz@gmail.com" },

{ipor_fusion-4.0.0.dev139 → ipor_fusion-4.0.0.dev144}/src/ipor_fusion/readers/oracle_mapping.py

@@ -433,8 +433,8 @@ def build_oracle_mapping(
 ) -> OracleMapping:
     """Build the full oracle mapping for ``vault``.
 
-    ``ctx`` must already be pinned to ``effective_block`` (the caller sets
-    ``ctx.default_block``); the block is echoed in the output. Raises
+    ``ctx`` must already be pinned to ``effective_block`` (pass
+    ``ctx.at_block(effective_block)``); the block is echoed in the output. Raises
     `UnsupportedVaultVersionError` for a vault that exposes no price-oracle
     getter.
     """

{ipor_fusion-4.0.0.dev139 → ipor_fusion-4.0.0.dev144}/tests/test_docs_typing.py

@@ -43,7 +43,11 @@ def _write_samples(directory: Path) -> dict[str, Path]:
 
 def test_doc_samples_type_check_as_a_consumer(tmp_path):
     modules = _write_samples(tmp_path)
-    assert {"README.md", "src/ipor_fusion/guide/quickstart.md"} <= set(modules)
+    assert {
+        "README.md",
+        "src/ipor_fusion/guide/quickstart.md",
+        "skills/ipor-deploy-vault/SKILL.md",
+    } <= set(modules)
     (tmp_path / "pyrightconfig.json").write_text(json.dumps(_CONSUMER_CONFIG))
     result = subprocess.run(  # noqa: S603 - fixed argv, the test's own interpreter
         [