fix: correct acap 2.0 start date#119
Merged
acaptutorials merged 3 commits intodevfrom May 2, 2026
Merged
Conversation
Aligned the ACAP 2.0 start date to when active development started in its code repository: October 2023 Note: - Previous date (June 2024) reflects official release, not development start. - Feature development for ACAP 2.1 continued beyond June 2024 - Dec 2024 in the acap-v2 dev branch, as reflected in ongoing commits following the ACAP 2.0 release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix: aligned the ACAP 2.0 start date to when active development started (October 2023) in the Changelog
Note:
devbranch, as reflected in ongoing commits following the ACAP 2.0 release.Chore: replaced FIREBASE_TOKEN with GCP_SA_KEY for Firebase Hosting deployment since FIREBASE_TOKEN usage is now deprecated