Feast follows semantic versions. Being pre-1.0, Feast is still considered in active initial development as per the SemVer spec.

That being said, Feast takes backwards compatibility seriously, to ensure that introducing new functionality across minor versions does not break current users.

When possible, API changes should always be made in a backwards compatible way. If this is not possible, the maintainers introduce new APIs alongside existing, now-deprecated APIs, with the intention of supporting the existing APIs for at least 3 minor versions, before deprecating and removing them. In some cases, the deprecated APIs may be supported for longer than 3 minor versions, if necessary to give users a longer time for migrations.

When deprecating existing APIs, deprecation warnings should be introduced early, with the expected version at which the deprecated API would be removed.

At this point, core functionality in Feast is considered "stable" and ready for usage. However, there are still some components that are considered "Alpha". Please check the roadmap for a full list of all capabilities and their status.

Setting up your environment

Please see the for project level development instructions and for specific details on how to set up your develop environment and contribute to Feast.

Maintainers Development

In most scenarios, your code changes or the areas of Feast that you are actively maintaining will only touch parts of the code(e.g one offline store/online store).

Forked Repo Best Practices

1. You should setup your fork so that you can make pull requests against your own master branch.

   • This prevents unnecessary integration tests and other github actions that are irrelevant to your code changes from being run everytime you would like to make a code change.

   • NOTE: Most workflows are enabled by default so manually that are not needed.

2. When you are ready to merge changes into the official feast branch, make a pull request with the main feast branch and request a review from other maintainers.

   • Since your code changes should only touch tests that are relevant to your functionality, and other tests should pass as well.

NOTE: Remember to frequently sync your fork master branch with feast-dev/feast:master.

Github Actions Workflow on Fork

• Recommended: The github actions workflows that should be enabled on the fork are as follows:

  • unit-tests

    • Runs all of the unit tests that should always pass.

  • linter

    • Lints your pr for styling or complexity issues using mypy, isort, and flake.

  • fork-pr-integration-tests-[provider]

    • Run all of the integration tests to test Feast functionality on your fork for a specific provider.

    • The .github/workflows folder has examples of common workflows(aws, gcp, and snowflake).

      1. Move the fork_pr_integration_tests_[provider].yml from .github/fork_workflows to .github/workflows.

      2. Edit fork_pr_integration_tests_[provider].yml (more details below) to only run the integration tests that are relevant to your area of interest.

      3. Push the workflow to your branch and it should automatically be added to the actions on your fork.

  • build_wheels

    • Release verification workflow to use for .

Integration Test Workflow Changes

Fork specific integration tests are run by the fork_pr_integration_tests.yml_[provider] yaml workflow files.

1. Under the integration-test-python job, replace your github repo with your feast github repo name.

2. If your offline store/online store needs special setup, add it to the job similar to how gcp is setup.
3. • Access these by setting environment variables as secrets.SECRET_NAME.

4. To limit pytest in your github workflow to test only your specific tests, leverage the -k option for pytest.

   • Each test in Feast is parametrized by its offline and online store so we can filter out tests by name. The above command chooses only tests with BigQuery that do not use Dynamo or Redshift.

5. Everytime a pull request or a change to a pull request is made, the integration tests, the local integration tests, the unit tests, and the linter should run.