Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 0 additions & 22 deletions .changeset/loud-spiders-end.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/sour-years-clap.md

This file was deleted.

27 changes: 27 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,32 @@
# chainlink-deployments-framework

## 0.61.0

### Minor Changes

- [#552](https://github.com/smartcontractkit/chainlink-deployments-framework/pull/552) [`32b13c5`](https://github.com/smartcontractkit/chainlink-deployments-framework/commit/32b13c5964a6d9234bb0342140ff8ca14c36da79) Thanks [@ajaskolski](https://github.com/ajaskolski)! - feat: add catalog service integration for datastore operations

Features:

- Add catalog service support for datastore management as alternative to local file storage
- Add `MergeMigrationDataStoreCatalog` method for catalog-based datastore persistence
- Existing `MergeMigrationDataStore` method continues to work for file-based storage (no breaking changes)
- Add unified `MergeDataStoreToCatalog` function for both initial migration and ongoing merge operations
- All catalog operations are transactional to prevent data inconsistencies
- Add `DatastoreType` configuration option (`file`/`catalog`) in domain.yaml to control storage backend
- Add new CLI command `datastore sync-to-catalog` for initial migration from file-based to catalog storage in CI
- Add `SyncDataStoreToCatalog` method to sync entire local datastore to catalog
- CLI automatically selects the appropriate merge method based on domain.yaml configuration
- Catalog mode does not modify local files - all updates go directly to the catalog service

Configuration:

- Set `datastore: catalog` in domain.yaml to enable catalog mode
- Set `datastore: file` or omit the setting to use traditional file-based storage
- CLI commands automatically detect the configuration and use the appropriate storage backend

- [#549](https://github.com/smartcontractkit/chainlink-deployments-framework/pull/549) [`3e33b93`](https://github.com/smartcontractkit/chainlink-deployments-framework/commit/3e33b93b9b99f25dfb25ad38f0baf4815245da2d) Thanks [@jkongie](https://github.com/jkongie)! - Improve JD Memory client to be aligned with the Job Distributor implementation

## 0.60.1

### Patch Changes
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "chainlink-deployments-framework",
"version": "0.60.1",
"version": "0.61.0",
"description": "A deployment framework for chainlink-deployments ",
"private": true,
"scripts": {
Expand Down
Loading