Bump @radixdlt/babylon-gateway-api-sdk from 1.2.0 to 1.4.1

[dependabot]

Bumps @radixdlt/babylon-gateway-api-sdk from 1.2.0 to 1.4.1.

Release notes

Sourced from @​radixdlt/babylon-gateway-api-sdk's releases.

1.4.1

Overview

This is the v1.4.1 release for the Gateway. API docs are on Redocly here: https://radix-babylon-gateway-api.redoc.ly/

License

The Babylon Gateway code is released under the Radix License. Binaries/Executable components are licensed under the Radix Software EULA.

Notes for Gateway runners

[!CAUTION] To properly fix all data, specific order of deployment is required.

1. Upgrade Data aggregator and Gateway API image
2. Execute Database migrations

If that order is not preserved and migrations are executed before the data aggregator is deployed some invalid entries might slip in.

What’s new?

Bug fixes

• Recreated key value store keys are properly returned from /state/key-value-store/keys and /state/key-value-store/data. Previously Gateway did not return keys that were deleted and then recreated. This release fixes existing data in the database and makes sure new ingested data is properly stored in the database.

Note to Integrators

Please note that the Babylon Core API on the Node is more powerful than on Olympia.

Integrators looking to prepare for the Radix Babylon launch should start by considering if running their own node and using the Core API would work instead of running a Gateway and using the Gateway API.

Please see the guide for integrators here.

Running just a node is simpler than running a node and Gateway, and the Core API has a "long term support" section of the API, designed for tracking fungible balances and accounts, which is guaranteed to be compatible with mainnet launch - enabling integrators to prepare for mainnet launch immediately.

Docker Images

This release is available as tag v1.4.1 on dockerhub, for the following images:

• radixdlt/babylon-ng-database-migrations
• radixdlt/babylon-ng-aggregator
• radixdlt/babylon-ng-gateway-api

1.4.0

Overview

This is the v1.4.0 release for the Gateway. API docs are on Redocly here: https://radix-babylon-gateway-api.redoc.ly/

License

The Babylon Gateway code is released under the Radix License. Binaries/Executable components are licensed under the Radix Software EULA.

... (truncated)

Changelog

Sourced from @​radixdlt/babylon-gateway-api-sdk's changelog.

1.4.1

Release built: 27.02.2024

Bug fixes

• Recreated key value store keys are properly returned from /state/key-value-store/keys and /state/key-value-store/keys. Previously Gateway did not return keys that were deleted and then recreated. This release fixes existing data in the database and makes sure new ingested data is properly stored in the database.

1.4.0

Release built: 08.02.2024

• Dropped internal balance_changes fallback mechanism. As of right now this information is ingested as part of regular transaction ingestion process.
• Reworked internal mechanism used to fetch network configuration. Is no longer stored in the underlying database and it is shared across all services.
• Reworked (partially) internal mechanism used to ingest ledger data by Data Aggregator to improve maintainability and simplify future extensions.
• Fixed state_version-based ledger state at_ledger_state/from_ledger_state constraints which could result in inaccurate lookups previously. Attempt to read from non-existent state version will result in HTTP 400 Bad Request. Previously the nearest state version would be used.

API Changes

• Return components effective role assignments only for assigned modules.
• Added new filters for the /stream/transactions endpoint: accounts_with_manifest_owner_method_calls, accounts_without_manifest_owner_method_calls and manifest_class_filter.
• Extended response models returned by /transaction/committed-details and /stream/transactions endpoints:
  • added manifest_instructions optional property and a corresponding opt-in for returning original manifest of user transactions,
  • added optional manifest_classes property: a collection of zero or more manifest classes ordered from the most specific class to the least specific one.
• Added permanently_rejects_at_epoch to /transaction/status response for pending transactions.
• Added new endpoint /state/key-value-store/keys/ that allows iterating over KeyValueStore keys.

Database changes

• Created new key_value_store_aggregate_history table which will hold pointers to all key_value_store keys.
• Dropped network_configuration table.
• Fixed component's method royalty aggregation, added missing component_method_royalty_aggregate_history table.
• Changed IX_validator_emission_statistics_validator_entity_id_epoch_num~ index to include proposals_made and proposals_missed columns in order to optimize /statistics/validators/update endpoint.

Deprecations

• Obsoleted incorrectly named access_rules_package in favor of role_assignment_module_package on NetworkConfigurationResponse.well_known_addresses. Obsoleted property will contain effective copy of the new one for backwards compability.

1.3.0

Release built: 29.01.2024

Adds support for protocol updates (in general) and the anemone update in particular.

API Changes

• Adds support for a new transaction type (flash transactions) that occur during protocol updates.
• Extends well known addresses returned from /status/network-configuration to include the transaction tracker address.
• DEPRECATION - Obsoletes the vm_type, code_hash_hex and code_hex properties of StateEntityDetailsResponsePackageDetails in favor of the codes collection. With the upcoming protocol upgrade it will be possible to have multiple codes per package. The obsoleted properties will contain an effective copy of the first element of the new collection for backwards compability.

Database changes

• Moves vm_type to package_code_history table from package in entity table.
• Creates new package_blueprint_aggregate_history table which will hold pointers to all package blueprints.
• Creates new package_code_aggregate_history table which will hold pointers to all package codes.

1.2.5

... (truncated)

Commits

• 2054f06 Merge pull request #665 from radixdlt/release/v1.4.1
• 254e0d8 include idempotent apply migrations.sql
• fbb8ad5 set value to null for deleted entries.
• 636ed02 fix sql script to recreate that base don aggregate table.
• b1eb74c fix recreating key value store keys. Make sure they are returned from gateway...
• 0ffaa14 Merge pull request #651 from radixdlt/documentation-update
• ec1d43e add information that multiple requests can target same state version.
• b4e64d1 Merge pull request #649 from radixdlt/fix/add-codeowners
• 3d54931 make it clear in changelog that it's date when image was built.
• b9250f2 update docs after David's review.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #7.