Release 0.0.115-rc.3

Release Notes Version: 0.0.115-rc3

Dear user, we believe in continuous improvement, so here we are again with yet another version update. Play celebratory trumpet sounds. The upgrades might not be apparent, but boy, have we been working hard behind the scenes!

1. README.md Update: The herding cats didn't seem to do the trick, so we have updated the gif file's source link. Now, crossing our fingers, the herding_cats.gif image should load just fine and not cause any 404 crisis. Thank your patience!

2. Lasereyes-core Version Update: You might not have noticed, but we actually changed our lasereyes-core version from 0.0.39 to 0.0.40-rc.2. Yep, we're that attentive to details. Next stop, world domination!

3. Lasereyes-react Version Update: We have also updated lasereyes-react. Goodbye version 0.0.31, let's welcome the new and slightly improved version 0.0.32-rc.1. Because improvements matter, no matter how small they appear.

4. Global Version Update: And finally, we saved the best for the last. Drumrolls, please... we've nudged our global version from 0.0.114 to 0.0.115-rc.3! We're one step closer to version 1.0, friends. One jolly step closer.

5. Minor Dependencies Shift: Lastly, we have changed the dependency requirements within the lasereyes package for "@omnisat/lasereyes-core" and "@omnisat/lasereyes-react". They now point to workspace:*. There will be no apparent changes or impact due to this update, but we thought you'd like to know... just because.

CAUTION: Please avoid looking directly into the laser eyes. Enjoy the version update!

• Faithfully yours, LaserEyes team.

Version: 0.0.114-rc.1

Tiny step forward, giant leap for kind

• We've updated the version of @omnisat/lasereyes-core from 0.0.38 to 0.0.39-rc.1 - a minor bump. But, you know, even the Moon is reached by small steps, and we all know what's happened there, right?

• In the file op-net.ts, we've added ? after this.library for method removeListener. Now, if this.library decides to play hide and seek game, we're prepared. We're always one step ahead.

• Similar changes in the file unisat.ts are also observed. if (!this.library) return is the new mantra for method removeListener. We believe in treating every code file with equality.

• Paving way for the future, version in @omnisat/lasereyes-react has been moved up from 0.0.30 to 0.0.31-rc.0. Small progress, but we never despise humble beginnings.

• Following the trend, version in lasereyes got an update from 0.0.113 to 0.0.114-rc.1. We're keeping up with the trend, aren't we?

• Lastly, a teensy-weensy change in generate_release_notes.py. Someone was kind enough to correct the spellings of anything and other. We truly believe that every letter counts, literally!

Leaps and bounds are reserved for superheroes. For us, slight numerical tweaks are our bread and butter. So here’s to many more atomic yet significant bumps in versions to come! Cheers!

Version: 0.0.113-rc.18

"You'll Never See These Updates Coming" Release Notes

Oh hey there! Surprised to see you here, but since you are, let's talk about the changes in our swanky new update.

1. Your favorite @omnisat/lasereyes-core couldn't stay at "0.0.36-rc.5", because well, change is the only constant in life. It now boasts a shiny version "0.0.38-rc.6". Nothing gets rid of Monday blues like new version numbers, amirite?

2. In the spirit of the age-old tradition of "always leave things slightly better than you found them", @omnisat/lasereyes-react decided to shake things up from "0.0.29-rc.7" and stepped up to "0.0.30-rc.7". We’ve got a good feeling about the number '30'.

3. Raising the stakes, we present to you eight – count 'em, EIGHT – new additions to your @omnisat/lasereyes-react exports. Welcome LeatherLogo, MagicEdenLogo, OkxLogo, PhantomLogo, OylLogo, UnisatLogo, WizzLogo, and XverseLogo. More is always better, except when it’s worse. In this case, we're certain it's better.

4. Last, but not the least, the self-titled celebrity @omnisat/lasereyes has leapfrogged from the quaint "0.0.113-rc.16" to the majestic "0.0.113-rc.18". Yeah, you saw that right, we completely skipped 'rc.17'. Because we are mavericks who play by our own rules.

So, buckle up, update your packages, and remember – we make these changes because we care... and because it's our job.

Keep on shining folks! Until the next wave of updates sweeps us away!

Phew! So much work, so little praise. Presenting to you, dear (and often thankless) users, Version 0.0.104-rc.2. Your gift for being so committed to this journey with us. Let's check the upgrades, shall we?

1. Delight in GitHub Release Syntax: It seems our developers have finally learnt to name their GitHub releases properly. Goodbye "github.ref", Hello "github.ref_name"! It took us a couple of commits but hey, better late than never, right?

2. Version Updates: Routine stuff really, but we'll mention it like it matters (because it totally does):

   • "lasereyes-core" got an upgrade to version "0.0.34-rc.0" from "0.0.33". Whoop-de-doo!
   • "lasereyes-react" too, was updated to version "0.0.27-rc.2" from "0.0.26". We could almost see the anticipation in your eyes.
   • And don't forget "lasereyes" itself, bumped up to version "0.0.104-rc.2" from "0.0.103". Yep, we're growing up!

3. README file found a purpose! It finally broke free from '92 and is now '95. Watch out for those three new thrilling lines of whitespace. They may be invisible to the naked eye, but they're there!

4. We bid farewell to workspace dependencies. They were great, but we're just better apart (specifically moved from workspace to defined versions for lasereyes-core and lasereyes-react dependencies). It's not them, it's us.

5. Scrapped orphans: We made the hard decision to let go some packages that were just taking up space - now making your code (and life) cleaner. You're welcome!

Finally, while we're on the topic of things you didn't ask for, but we provide anyway, please marvel at our newfound passive aggressiveness. That's right dear folks, our release note generator script had an attitude adjustment. It will now churn out "detailed, sometimes hilarious release notes" instead of plain ol' "detailed" ones.

But don’t worry, we will "always ensure we are informative and helpful," even though the world may not always appreciate our cheeky sense of humor. Make sure you appreciate it (or else we might have to make other trivial, but time-consuming changes). Enjoy Leo (aka Version 0.0.104-rc.2)!

Release Notes for Version: 0.0.103-rc.18

Updates

1. In our Github action workflow for releases, we've added a new command to rebase the main branch from origin after the release notes commit is done. This will help to synchronize the main branch with any new commits made during the build process, ensuring that the following push to the main branch is up-to-date.

2. We've updated the version of lasereyes-core from 0.0.32 to 0.0.33-rc.3.

3. We've updated the version of lasereyes-react from 0.0.25 to 0.0.26-rc.7.

4. Version of the lasereyes package has been updated from 0.0.102 to 0.0.103-rc.18.

5. We now use workspace:* for dependencies on @omnisat/lasereyes-core and @omnisat/lasereyes-react.

Dependency Changes

1. In lasereyes package, the dependencies for @omnisat/lasereyes-core and @omnisat/lasereyes-react have switched from specific versions to workspace:*. This designates that the local versions of these packages should be used, which can speed up the development process as changes in the local packages are immediately available.

2. Our pnpm-lock.yaml file has been updated to indicate this shift to using the workspace packages. Now, instead of pointing to a specific version of the lasereyes-core and lasereyes-react packages, they point to the local workspace version.

Misc

Two empty line spaces have been added to the end of the @omnisat/lasereyes-react README.md file.

Release Notes

Enhancements

• The environment for the GitHub action workflow 'generate-release' is now set to 'prod'.

Package Updates

• Updated lasereyes-core package version from 0.0.0-rc.2 to 0.0.0-rc.3.
• Updated lasereyes package version from 0.0.37-rc.18 to 0.0.37-rc.19.

Documentation

• A test line has been added to the README.md file in the lasereyes-core package folder.

Release Notes

In this update, we've made several changes and improvements.

Changes

Update in GitHub Action Workflow Configuration

• The method to ensure single 'v' in tag_name has been modified. Now instead of taking tag_name from the env.lasereyes_version environment variable, it takes from needs.bump-versions-main.outputs.lasereyes_version output. This change is made in the .github/workflows/release.yml file.

Updates in Documentation

• In lasereyes-core package, a new paragraph "test" has been inserted at the end of the README file.

• Similarly, in lasereyes-react package, one more paragraph named "test" has also been added at the end of the README file.

Please make sure to update your cloned repositories to reflect these changes.

Release Notes

Configurations

• The git user is now configured in the GitHub workflow release.yml file. The user email is set to "github-actions[bot]@users.noreply.github.com" and the username set to "github-actions[bot]".

lasereyes-react package

• Updated the version of the lasereyes-react package from 0.0.1 to 0.0.0-rc.18 in both, the package.json and the package-lock.json files.

• An additional test line was added to the README.md file of lasereyes-react.

lasereyes package

• Downgraded the version of the lasereyes package from 0.0.38 to 0.0.37-rc.17 in the package.json file.

All of these changes are meant to better the reliability and functionality of the package. Please update your packages to these versi...

Release 0.0.114-rc.1

Version: 0.0.114-rc.1

Tiny step forward, giant leap for kind

• We've updated the version of @omnisat/lasereyes-core from 0.0.38 to 0.0.39-rc.1 - a minor bump. But, you know, even the Moon is reached by small steps, and we all know what's happened there, right?

• In the file op-net.ts, we've added ? after this.library for method removeListener. Now, if this.library decides to play hide and seek game, we're prepared. We're always one step ahead.

• Similar changes in the file unisat.ts are also observed. if (!this.library) return is the new mantra for method removeListener. We believe in treating every code file with equality.

• Paving way for the future, version in @omnisat/lasereyes-react has been moved up from 0.0.30 to 0.0.31-rc.0. Small progress, but we never despise humble beginnings.

• Following the trend, version in lasereyes got an update from 0.0.113 to 0.0.114-rc.1. We're keeping up with the trend, aren't we?

• Lastly, a teensy-weensy change in generate_release_notes.py. Someone was kind enough to correct the spellings of anything and other. We truly believe that every letter counts, literally!

Leaps and bounds are reserved for superheroes. For us, slight numerical tweaks are our bread and butter. So here’s to many more atomic yet significant bumps in versions to come! Cheers!

Version: 0.0.113-rc.18

"You'll Never See These Updates Coming" Release Notes

Oh hey there! Surprised to see you here, but since you are, let's talk about the changes in our swanky new update.

1. Your favorite @omnisat/lasereyes-core couldn't stay at "0.0.36-rc.5", because well, change is the only constant in life. It now boasts a shiny version "0.0.38-rc.6". Nothing gets rid of Monday blues like new version numbers, amirite?

2. In the spirit of the age-old tradition of "always leave things slightly better than you found them", @omnisat/lasereyes-react decided to shake things up from "0.0.29-rc.7" and stepped up to "0.0.30-rc.7". We’ve got a good feeling about the number '30'.

3. Raising the stakes, we present to you eight – count 'em, EIGHT – new additions to your @omnisat/lasereyes-react exports. Welcome LeatherLogo, MagicEdenLogo, OkxLogo, PhantomLogo, OylLogo, UnisatLogo, WizzLogo, and XverseLogo. More is always better, except when it’s worse. In this case, we're certain it's better.

4. Last, but not the least, the self-titled celebrity @omnisat/lasereyes has leapfrogged from the quaint "0.0.113-rc.16" to the majestic "0.0.113-rc.18". Yeah, you saw that right, we completely skipped 'rc.17'. Because we are mavericks who play by our own rules.

So, buckle up, update your packages, and remember – we make these changes because we care... and because it's our job.

Keep on shining folks! Until the next wave of updates sweeps us away!

Phew! So much work, so little praise. Presenting to you, dear (and often thankless) users, Version 0.0.104-rc.2. Your gift for being so committed to this journey with us. Let's check the upgrades, shall we?

1. Delight in GitHub Release Syntax: It seems our developers have finally learnt to name their GitHub releases properly. Goodbye "github.ref", Hello "github.ref_name"! It took us a couple of commits but hey, better late than never, right?

2. Version Updates: Routine stuff really, but we'll mention it like it matters (because it totally does):

   • "lasereyes-core" got an upgrade to version "0.0.34-rc.0" from "0.0.33". Whoop-de-doo!
   • "lasereyes-react" too, was updated to version "0.0.27-rc.2" from "0.0.26". We could almost see the anticipation in your eyes.
   • And don't forget "lasereyes" itself, bumped up to version "0.0.104-rc.2" from "0.0.103". Yep, we're growing up!

3. README file found a purpose! It finally broke free from '92 and is now '95. Watch out for those three new thrilling lines of whitespace. They may be invisible to the naked eye, but they're there!

4. We bid farewell to workspace dependencies. They were great, but we're just better apart (specifically moved from workspace to defined versions for lasereyes-core and lasereyes-react dependencies). It's not them, it's us.

5. Scrapped orphans: We made the hard decision to let go some packages that were just taking up space - now making your code (and life) cleaner. You're welcome!

Finally, while we're on the topic of things you didn't ask for, but we provide anyway, please marvel at our newfound passive aggressiveness. That's right dear folks, our release note generator script had an attitude adjustment. It will now churn out "detailed, sometimes hilarious release notes" instead of plain ol' "detailed" ones.

But don’t worry, we will "always ensure we are informative and helpful," even though the world may not always appreciate our cheeky sense of humor. Make sure you appreciate it (or else we might have to make other trivial, but time-consuming changes). Enjoy Leo (aka Version 0.0.104-rc.2)!

Release Notes for Version: 0.0.103-rc.18

Updates

1. In our Github action workflow for releases, we've added a new command to rebase the main branch from origin after the release notes commit is done. This will help to synchronize the main branch with any new commits made during the build process, ensuring that the following push to the main branch is up-to-date.

2. We've updated the version of lasereyes-core from 0.0.32 to 0.0.33-rc.3.

3. We've updated the version of lasereyes-react from 0.0.25 to 0.0.26-rc.7.

4. Version of the lasereyes package has been updated from 0.0.102 to 0.0.103-rc.18.

5. We now use workspace:* for dependencies on @omnisat/lasereyes-core and @omnisat/lasereyes-react.

Dependency Changes

1. In lasereyes package, the dependencies for @omnisat/lasereyes-core and @omnisat/lasereyes-react have switched from specific versions to workspace:*. This designates that the local versions of these packages should be used, which can speed up the development process as changes in the local packages are immediately available.

2. Our pnpm-lock.yaml file has been updated to indicate this shift to using the workspace packages. Now, instead of pointing to a specific version of the lasereyes-core and lasereyes-react packages, they point to the local workspace version.

Misc

Two empty line spaces have been added to the end of the @omnisat/lasereyes-react README.md file.

Release Notes

Enhancements

• The environment for the GitHub action workflow 'generate-release' is now set to 'prod'.

Package Updates

• Updated lasereyes-core package version from 0.0.0-rc.2 to 0.0.0-rc.3.
• Updated lasereyes package version from 0.0.37-rc.18 to 0.0.37-rc.19.

Documentation

• A test line has been added to the README.md file in the lasereyes-core package folder.

Release Notes

In this update, we've made several changes and improvements.

Changes

Update in GitHub Action Workflow Configuration

• The method to ensure single 'v' in tag_name has been modified. Now instead of taking tag_name from the env.lasereyes_version environment variable, it takes from needs.bump-versions-main.outputs.lasereyes_version output. This change is made in the .github/workflows/release.yml file.

Updates in Documentation

• In lasereyes-core package, a new paragraph "test" has been inserted at the end of the README file.

• Similarly, in lasereyes-react package, one more paragraph named "test" has also been added at the end of the README file.

Please make sure to update your cloned repositories to reflect these changes.

Release Notes

Configurations

• The git user is now configured in the GitHub workflow release.yml file. The user email is set to "github-actions[bot]@users.noreply.github.com" and the username set to "github-actions[bot]".

lasereyes-react package

• Updated the version of the lasereyes-react package from 0.0.1 to 0.0.0-rc.18 in both, the package.json and the package-lock.json files.

• An additional test line was added to the README.md file of lasereyes-react.

lasereyes package

• Downgraded the version of the lasereyes package from 0.0.38 to 0.0.37-rc.17 in the package.json file.

All of these changes are meant to better the reliability and functionality of the package. Please update your packages to these versions for an improved user experience.

Release Notes: v0.0.36

Detailed Updates:

General:

• Transitioned to new versioning format for the package, now using release candidate (rc) versioning.

Package Updates:

1. @omnisat/lasereyes-core:

   • The package version has been updated from "0.0.6" to "0.0.7-rc.0".

2. lasereyes-react:

   • The package version in the package-lock.json file was updated from "0.0.4" to "0.0.5-rc.0".
   • The package version in the package.json file got updated from "0.0.4" to "0.0.5-rc.0".

3. @omnisat/lasereyes:

   • The package version in the package.json file was updated from "0.0.36" to "0.0.37-rc.0".

Please note:

A release candidate (RC) version number indicates that the developers think the software is ready for its final release but want to make sure through testing; more changes may come before the final release, but they should be minor.

The updated packages should now be tested thoroughly before the final release.

These changes help to better track the progress of new features and bug fixes, by providing an advanced snapshot of what's changing in each package.

Release Notes for Version: v0.0.35

In this new version, several updates have been made to the packages, mainly targeting:

1. Lasereyes-core:

   The package version has been upgraded from v0.0.5 to a release candidate v0.0.6-rc.0. This release candidate will undergo further testing before a full version update.

2. Lasereyes-react:

   Both the package.json and package-lock.json files have been updated. The package version has been updated from `v0.0.3...

Release 0.0.113-rc.18

Version: 0.0.113-rc.18

"You'll Never See These Updates Coming" Release Notes

Oh hey there! Surprised to see you here, but since you are, let's talk about the changes in our swanky new update.

1. Your favorite @omnisat/lasereyes-core couldn't stay at "0.0.36-rc.5", because well, change is the only constant in life. It now boasts a shiny version "0.0.38-rc.6". Nothing gets rid of Monday blues like new version numbers, amirite?

2. In the spirit of the age-old tradition of "always leave things slightly better than you found them", @omnisat/lasereyes-react decided to shake things up from "0.0.29-rc.7" and stepped up to "0.0.30-rc.7". We’ve got a good feeling about the number '30'.

3. Raising the stakes, we present to you eight – count 'em, EIGHT – new additions to your @omnisat/lasereyes-react exports. Welcome LeatherLogo, MagicEdenLogo, OkxLogo, PhantomLogo, OylLogo, UnisatLogo, WizzLogo, and XverseLogo. More is always better, except when it’s worse. In this case, we're certain it's better.

4. Last, but not the least, the self-titled celebrity @omnisat/lasereyes has leapfrogged from the quaint "0.0.113-rc.16" to the majestic "0.0.113-rc.18". Yeah, you saw that right, we completely skipped 'rc.17'. Because we are mavericks who play by our own rules.

So, buckle up, update your packages, and remember – we make these changes because we care... and because it's our job.

Keep on shining folks! Until the next wave of updates sweeps us away!

Phew! So much work, so little praise. Presenting to you, dear (and often thankless) users, Version 0.0.104-rc.2. Your gift for being so committed to this journey with us. Let's check the upgrades, shall we?

1. Delight in GitHub Release Syntax: It seems our developers have finally learnt to name their GitHub releases properly. Goodbye "github.ref", Hello "github.ref_name"! It took us a couple of commits but hey, better late than never, right?

2. Version Updates: Routine stuff really, but we'll mention it like it matters (because it totally does):

   • "lasereyes-core" got an upgrade to version "0.0.34-rc.0" from "0.0.33". Whoop-de-doo!
   • "lasereyes-react" too, was updated to version "0.0.27-rc.2" from "0.0.26". We could almost see the anticipation in your eyes.
   • And don't forget "lasereyes" itself, bumped up to version "0.0.104-rc.2" from "0.0.103". Yep, we're growing up!

3. README file found a purpose! It finally broke free from '92 and is now '95. Watch out for those three new thrilling lines of whitespace. They may be invisible to the naked eye, but they're there!

4. We bid farewell to workspace dependencies. They were great, but we're just better apart (specifically moved from workspace to defined versions for lasereyes-core and lasereyes-react dependencies). It's not them, it's us.

5. Scrapped orphans: We made the hard decision to let go some packages that were just taking up space - now making your code (and life) cleaner. You're welcome!

Finally, while we're on the topic of things you didn't ask for, but we provide anyway, please marvel at our newfound passive aggressiveness. That's right dear folks, our release note generator script had an attitude adjustment. It will now churn out "detailed, sometimes hilarious release notes" instead of plain ol' "detailed" ones.

But don’t worry, we will "always ensure we are informative and helpful," even though the world may not always appreciate our cheeky sense of humor. Make sure you appreciate it (or else we might have to make other trivial, but time-consuming changes). Enjoy Leo (aka Version 0.0.104-rc.2)!

Release Notes for Version: 0.0.103-rc.18

Updates

1. In our Github action workflow for releases, we've added a new command to rebase the main branch from origin after the release notes commit is done. This will help to synchronize the main branch with any new commits made during the build process, ensuring that the following push to the main branch is up-to-date.

2. We've updated the version of lasereyes-core from 0.0.32 to 0.0.33-rc.3.

3. We've updated the version of lasereyes-react from 0.0.25 to 0.0.26-rc.7.

4. Version of the lasereyes package has been updated from 0.0.102 to 0.0.103-rc.18.

5. We now use workspace:* for dependencies on @omnisat/lasereyes-core and @omnisat/lasereyes-react.

Dependency Changes

1. In lasereyes package, the dependencies for @omnisat/lasereyes-core and @omnisat/lasereyes-react have switched from specific versions to workspace:*. This designates that the local versions of these packages should be used, which can speed up the development process as changes in the local packages are immediately available.

2. Our pnpm-lock.yaml file has been updated to indicate this shift to using the workspace packages. Now, instead of pointing to a specific version of the lasereyes-core and lasereyes-react packages, they point to the local workspace version.

Misc

Two empty line spaces have been added to the end of the @omnisat/lasereyes-react README.md file.

Release Notes

Enhancements

• The environment for the GitHub action workflow 'generate-release' is now set to 'prod'.

Package Updates

• Updated lasereyes-core package version from 0.0.0-rc.2 to 0.0.0-rc.3.
• Updated lasereyes package version from 0.0.37-rc.18 to 0.0.37-rc.19.

Documentation

• A test line has been added to the README.md file in the lasereyes-core package folder.

Release Notes

In this update, we've made several changes and improvements.

Changes

Update in GitHub Action Workflow Configuration

• The method to ensure single 'v' in tag_name has been modified. Now instead of taking tag_name from the env.lasereyes_version environment variable, it takes from needs.bump-versions-main.outputs.lasereyes_version output. This change is made in the .github/workflows/release.yml file.

Updates in Documentation

• In lasereyes-core package, a new paragraph "test" has been inserted at the end of the README file.

• Similarly, in lasereyes-react package, one more paragraph named "test" has also been added at the end of the README file.

Please make sure to update your cloned repositories to reflect these changes.

Release Notes

Configurations

• The git user is now configured in the GitHub workflow release.yml file. The user email is set to "github-actions[bot]@users.noreply.github.com" and the username set to "github-actions[bot]".

lasereyes-react package

• Updated the version of the lasereyes-react package from 0.0.1 to 0.0.0-rc.18 in both, the package.json and the package-lock.json files.

• An additional test line was added to the README.md file of lasereyes-react.

lasereyes package

• Downgraded the version of the lasereyes package from 0.0.38 to 0.0.37-rc.17 in the package.json file.

All of these changes are meant to better the reliability and functionality of the package. Please update your packages to these versions for an improved user experience.

Release Notes: v0.0.36

Detailed Updates:

General:

• Transitioned to new versioning format for the package, now using release candidate (rc) versioning.

Package Updates:

1. @omnisat/lasereyes-core:

   • The package version has been updated from "0.0.6" to "0.0.7-rc.0".

2. lasereyes-react:

   • The package version in the package-lock.json file was updated from "0.0.4" to "0.0.5-rc.0".
   • The package version in the package.json file got updated from "0.0.4" to "0.0.5-rc.0".

3. @omnisat/lasereyes:

   • The package version in the package.json file was updated from "0.0.36" to "0.0.37-rc.0".

Please note:

A release candidate (RC) version number indicates that the developers think the software is ready for its final release but want to make sure through testing; more changes may come before the final release, but they should be minor.

The updated packages should now be tested thoroughly before the final release.

These changes help to better track the progress of new features and bug fixes, by providing an advanced snapshot of what's changing in each package.

Release Notes for Version: v0.0.35

In this new version, several updates have been made to the packages, mainly targeting:

1. Lasereyes-core:

   The package version has been upgraded from v0.0.5 to a release candidate v0.0.6-rc.0. This release candidate will undergo further testing before a full version update.

2. Lasereyes-react:

   Both the package.json and package-lock.json files have been updated. The package version has been updated from v0.0.3 to a release candidate version v0.0.4-rc.0 reflecting potential upcoming changes expected to be fully implemented in the version 0.0.4.

3. Lasereyes:

   The package version has been updated from v0.0.35 to a release candidate v0.0.36-rc.0.

Please note that all the updates are related to the versions of the packages. More information about any new features or fixes will be provided as they come in future updates. Until then, the users can continue with the same feature set as the previous version.

Release Notes

Version v0.0.34

Packages Updated

• @omnisat/lasereyes-core

  • Version bumped from 0.0.5-rc.3 to 0.0.5-rc.4.

• @omnisat/lasereyes-react

  • Updated package-lock.json and package.json files.
    • Version bumped from 0.0.3-rc.2 to 0.0.3-rc.3 in both files.

• @omnisat/lasereyes

  • Version updated from 0.0.34 to 0.0.35-rc.0 in the package.json file.

Summary

This release primarily involves updates to the package versions across the libraries for @omnisat/lasereyes-core, @omnisat/lasereyes-react, and @omnisat/lasereyes. No notable features or bug fixes were introduced in this version.

Release Notes - Version v0.0.33

General

New version v0.0.33 brings a few important updates across several packages. Enhancement in package versions are introduce...

Release v0.0.36

Release Notes: v0.0.36

Detailed Updates:

General:

• Transitioned to new versioning format for the package, now using release candidate (rc) versioning.

Package Updates:

1. @omnisat/lasereyes-core:

   • The package version has been updated from "0.0.6" to "0.0.7-rc.0".

2. lasereyes-react:

   • The package version in the package-lock.json file was updated from "0.0.4" to "0.0.5-rc.0".
   • The package version in the package.json file got updated from "0.0.4" to "0.0.5-rc.0".

3. @omnisat/lasereyes:

   • The package version in the package.json file was updated from "0.0.36" to "0.0.37-rc.0".

Please note:

A release candidate (RC) version number indicates that the developers think the software is ready for its final release but want to make sure through testing; more changes may come before the final release, but they should be minor.

The updated packages should now be tested thoroughly before the final release.

These changes help to better track the progress of new features and bug fixes, by providing an advanced snapshot of what's changing in each package.

Release v0.0.35

Release Notes for Version: v0.0.35

In this new version, several updates have been made to the packages, mainly targeting:

1. Lasereyes-core:

   The package version has been upgraded from v0.0.5 to a release candidate v0.0.6-rc.0. This release candidate will undergo further testing before a full version update.

2. Lasereyes-react:

   Both the package.json and package-lock.json files have been updated. The package version has been updated from v0.0.3 to a release candidate version v0.0.4-rc.0 reflecting potential upcoming changes expected to be fully implemented in the version 0.0.4.

3. Lasereyes:

   The package version has been updated from v0.0.35 to a release candidate v0.0.36-rc.0.

Please note that all the updates are related to the versions of the packages. More information about any new features or fixes will be provided as they come in future updates. Until then, the users can continue with the same feature set as the previous version.

Release v0.0.34

Release Notes

Version v0.0.34

Packages Updated

• @omnisat/lasereyes-core

  • Version bumped from 0.0.5-rc.3 to 0.0.5-rc.4.

• @omnisat/lasereyes-react

  • Updated package-lock.json and package.json files.
    • Version bumped from 0.0.3-rc.2 to 0.0.3-rc.3 in both files.

• @omnisat/lasereyes

  • Version updated from 0.0.34 to 0.0.35-rc.0 in the package.json file.

Summary

This release primarily involves updates to the package versions across the libraries for @omnisat/lasereyes-core, @omnisat/lasereyes-react, and @omnisat/lasereyes. No notable features or bug fixes were introduced in this version.

Release v0.0.33

Release Notes - Version v0.0.33

General

New version v0.0.33 brings a few important updates across several packages. Enhancement in package versions are introduced in this update.

Details

Here is the summary of the version changes:

• @omnisat/lasereyes-core
  The version has been updated from v0.0.5-rc.2 to v0.0.5-rc.3.

• lasereyes-react
  The versions in both package-lock.json and package.json files have been updated from v0.0.3-rc.1 to v0.0.3-rc.2.

• @omnisat/lasereyes
  The version has been updated from v0.0.33 to v0.0.34-rc.0.

Please note the new changes and update your packages accordingly for optimal performance and latest features.

Remember to always start with backing up your application and data before applying any updates. Make sure to test in a controlled environment that resembles your production environment before moving forward with these upgrades in your production environment.

Release v0.0.32

Release Notes

Version: v0.0.33-rc.0

In this new release, the main highlight is the version bump of @omnisat/lasereyes from version 0.0.32 to 0.0.33-rc.0. This new version is a release candidate and this change reflects the preparation for the next potential stable release.

No other documented changes were made to the codebase in this update.

Please note: This release, being a release candidate, is not intended for production use. It is released for testing purposes, to catch any critical issues before the final release.

Release v0.0.31

Release Notes

Version: v0.0.32-rc.0

Changes

• The package version has been updated from "0.0.31" to "0.0.32-rc.0". This signifies that we have moved onto the next release cycle.

Please note that this is a release candidate version(-rc.0), meaning it's not the final version. Rather, it's a version we believe to be stable and includes all features we intend to deliver, but it's not yet thoroughly tested to be declared as stable.

Remember to update your dependencies to ensure compatibility with this new version.

Release v0.0.30

Release Notes for v0.0.31-rc.0

Updates:

1. Version Upgrade: The package has been upgraded from version 0.0.30 to version 0.0.31-rc.0.

No additional changes have been made in the package's modules or structure as per the git diff provided. Please ensure to update your dependencies to stay up-to-date with the latest features and improvements of the "@omnisat/lasereyes" package.