v0.7.0

What's changed?

• Add support for Meta Transactions NEP-366 by upgrading near-indexer-primitives to 0.16
• Add helper function for connecting to betanet lake

Breaking change

• Delegate action has been introduced in near-primitives::views::ActionView, this should be handled everywhere you are handling ActionView
  Crate Link: https://crates.io/crates/near-lake-framework/0.7.0
  Full Changelog: v0.6.1...v0.7.0

v0.6.1

What's changed?

• Fix of possible silent stops of the streamer (firing logs and returning errors where necessary)
• Fix the issue the streamer was always 1 block behind
• Renamed a few internal methods to reflect what they do
• Added debug and error logs in a few places
• Introduced a LakeError enum using thiserror (#42), but not exposing it yet to avoid breaking changes to the framework (for now, it will be done in 0.7.0)
• Added proper error handling in a few places
• Updated the dependencies version of AWS crates
  Crate Link: https://crates.io/crates/near-lake-framework/0.6.1
  Full Changelog: v0.6.0...v0.6.1

v0.6.0

What's changed?

• Upgrade underlying dependency near-indexer-primitives to versions between 0.15 and 0.16

Breaking change

near-indexer-primitives reflects some breaking changes in the data types. Some of the fields that were previously
a base64-encoded String that now became raw Vec<u8>:

• views::ActionView::FunctionCall.args
• views::QueryResponseKind::ViewState
• views::ExecutionStatusView::SuccessValue

Refer to this nearcore commit to find all the changes of this kind.
Crate Link: https://crates.io/crates/near-lake-framework/0.6.0
Full Changelog: v0.5.2...v0.6.0

v0.5.2

What's changed?

• Fixed the bug that caused a lag by 100 blocks that was introduced in 0.5.1
  Crate Link: https://crates.io/crates/near-lake-framework/0.5.2
  Full Changelog: v0.5.1...v0.5.2

v0.5.1

What's changed?

• Avoid spiky latency with streaming block heights preload
  Crate Link: https://crates.io/crates/near-lake-framework/0.5.1
  Full Changelog: v0.5.0...v0.5.1

v0.5.0

What's changed?

• Cleaned up unused depdendencies
• Added the configuration option to control the size of the pool of
  preloaded blocks blocks_preload_pool_size (100 remains to be the default)
• Update AWS dependencies to 0.13.0

Breaking change

• Dropped the previously allowed way to instantiate LakeConfig by manually
  initializing the public fields in favor of
  the builder pattern
  Crate Link: https://crates.io/crates/near-lake-framework/0.5.0
  Full Changelog: v0.4.1...v0.5.0

v0.4.1

What's changed?

• Bumped the minimum required version of serde_json to 1.0.75 to avoid
  confusing errors when arbitrary_precision feature is enabled.
• Extended the list of supported near-primitives versions from 0.12.0
  to >=0.12.0,<0.15.0 to help downstream project avoid duplicate versions
  of near-primitives and its dependencies.
• Reduced verbosity level of recoverable errors from ERROR to WARN
  Crate Link: https://crates.io/crates/near-lake-framework/0.4.1
  Full Changelog: v0.4.0...v0.4.1

v0.4.0

What's changed?

• Remove calls to .unwrap() and .expect() within the stream sender that
  could panic. Instead, a Result is returned from the sender task. (@joel-u410)
• Remove calls to .unwrap() and .expect() within s3_fetchers module

Breaking change

• The streamer() function now returns a tuple, with the first element being a
  JoinHandle<Result<(), Error>> that you can use to gracefully capture any
  errors that occurred within the sender task. If you don't care about errors,
  you can easily adapt to this change by changing:

  let receiver = near_lake_framework::streamer(settings);

  to this instead:

  let (_, receiver) = near_lake_framework::streamer(settings);

Crate Link: https://crates.io/crates/near-lake-framework/0.4.0
Full Changelog: v0.3.0...v0.4.0

v0.3.0

What's changed?

• Introduce LakeConfigBuilder for creating configs

  let config = LakeConfigBuilder.default()
    .testnet()
    .start_block_height(88220926)
    .build()
    .expect("Failed to build LakeConfig");

• Now you can provide custom AWS SDK S3 Config

  use aws_sdk_s3::Endpoint;
  use http::Uri;
  use near_lake_framework::LakeConfigBuilder;
  
  let aws_config = aws_config::from_env().load().await;
  let mut s3_conf = aws_sdk_s3::config::Builder::from(&aws_config);
  s3_conf = s3_conf
    .endpoint_resolver(
      Endpoint::immutable("http://0.0.0.0:9000".parse::<Uri>().unwrap()))
    .build();
  
  let config = LakeConfigBuilder::default()
    .s3_config(s3_conf)
    .s3_bucket_name("near-lake-data-custom")
    .start_block_height(1)
    .build()
    .expect("Failed to build LakeConfig");

Breaking change

LakeConfig has a breaking change as we've removed s3_endpoint and added s3_config. Please, consider migrating to use LakeConfigBuilder instead of directly crafting the Lakeconfig

Crate Link: https://crates.io/crates/near-lake-framework/0.3.0
Full Changelog: v0.2.0...v0.3.0

v0.2.0

What's changed?

The first public release. See announcement on NEAR Gov Forum

Release Page: https://github.com/near/near-lake-framework/releases/tag/v0.2.0

Crate Link: https://crates.io/crates/near-lake-framework/0.2.0