Changelog

Stay up to date with the latest Fire Opal release notes

We follow the Semantic Versioning standard.

Fire Opal 6.7.0

January 26, 2024

What's new

  • Things have changed, but the differences shouldn't be materially noticeable for you...kind of like the subatomic world.

Fire Opal 6.6.0

November 14, 2023

What's new

  • Fire Opal now supports API key-based authentication! This feature enables you to use Fire Opal from web or cloud-based environments without having to authenticate via a browser. Take a look at the user guide to learn how to use the feature.

Fire Opal 6.5.0

October 18, 2023

What's new

  • We added a credentials builder for IBM Cloud device access make_credentials_for_ibm_cloud.

Fire Opal 6.4.1

October 16, 2023

What's new

  • More updates to keep the lights on.

Fire Opal 6.4.0

October 13, 2023

What's new

  • Fire Opal now supports 27-qubit devices! You can use ibm_algiers through Fire Opal at no added cost (besides what you would be paying on IBM Cloud for compute). For access to Premium devices through Fire Opal, please reach out to us.
  • You can now package your credentials for ibm_cloud using the credentials builder function make_credentials_for_ibm_cloud.

Fire Opal 6.3.0

October 10, 2023

What's new

  • We released a new feature called the activity_monitor. This enables you to see your previously executed jobs and their IDs and statuses.
  • Using the Job ID, you can retrieve the execution results using the new get_result function.

Fire Opal 6.2.1

September 21, 2023

What's new

  • Internal dependency updates

Fire Opal 6.2.0

September 14, 2023

What's new

  • Added a version check when the package is imported.

Fire Opal 6.1.1

September 1, 2023

What's new

  • Fixing up some stuff behind the scenes.

Fire Opal 6.1.0

August 21, 2023

What's new

  • The execute function now accepts a single QASM circuit (str) in addition to a list of circuits (list[str]).
  • We also added type checks in the execute function to save you from banging your head on the keyboard while debugging an error caused by inputting the wrong object as a parameter.

Next