Release 1.4 ( .net 8 upgrade) #518
Merged
Conversation
This file contains 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
…rently copied into casdk-docs/docs to get live updates (copied and not moved so changes in main can be easily identified when rebasing once it all works)
DRAFT - Docs/docusaurus setup
Signed-off-by: Phil Huang <[email protected]>
Signed-off-by: tkuramoto33 <[email protected]>
Signed-off-by: tkuramoto33 <[email protected]>
Signed-off-by: tkuramoto33 <[email protected]>
table of content Signed-off-by: Rintaro Ikeda <[email protected]>
Signed-off-by: Rintaro Ikeda <[email protected]>
Small typo ("arbon" => "Carbon")
Signed-off-by: Richard Jackson <[email protected]>
Update WattTime registration link
Signed-off-by: omahs <[email protected]>
Signed-off-by: omahs <[email protected]>
Migrate to .NET 8
Signed-off-by: Sophie Trinder <[email protected]>
Update agenda-template.md
Signed-off-by: Yasumasa Suenaga <[email protected]>
[URGENT] WebAPI container has not built due to segmentation fault
Fix typos in documentation
Creating the case study template. Signed-off-by: Vaughan Knight <[email protected]>
Minor updates. Signed-off-by: Vaughan Knight <[email protected]>
Signed-off-by: Yasumasa Suenaga <[email protected]>
Signed-off-by: Dan Benitah <[email protected]>
I, joecus1 <[email protected]>, hereby add my Signed-off-by to this commit: c6b2c14 Signed-off-by: joecus1 <[email protected]>
update older .Net reference Signed-off-by: nttDamien <[email protected]>
Signed-off-by: nttDamien <[email protected]>
Signed-off-by: nttDamien <[email protected]>
2 missed references... Signed-off-by: nttDamien <[email protected]>
Update published documentation to .NET 8
overview.md: Fixed three broken links Signed-off-by: joecus1 <joecusa…
Signed-off-by: Vaughan Knight <[email protected]>
10 tasks
45 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request
Issue Number: (Link to Github Issue or Azure Dev Ops Task/Story)
Summary
Release 1.4 for .net 8 upgrade
Changes
[1.4.0] - 2024-05
Added
-[#401] [Feature Contribution]: Upgrade .NET version to .NET 8 ](#401)
-[#419] [Feature Contribution]: Migrate sample implementation of Azure Function to isolated worker model ](#419)
-[PR #500] Up Helm chart version to 1.2.0 ](#500)
-[#397] [Feature Contribution]: Data caching in the SDK ](#397)
Fixed
-[#505] [Bug]: Project Page wiki from GSF website still says it's in incubation ](#505)
-[#496] [URGENT] WebAPI container has not built due to segmentation fault ](#496)
-[#487] [Bug]: Getting started guide is lost ](#487)
Changed
-[#477] [Bug]: Ensure the readme file shows as the project overview content on the documentation site ](#477)
-[PR #485] Docs overview, disclaimer & pipeline updates for graduation ](#485)
API
API Deployment
SDK
Other
For more details, checkout #503
Checklist
Are there API Changes?
If yes, what are the expected API Changes? Please link to an API-Comparison
workflow with the API Diff.
Is this a breaking change?
If yes, what workflow does this break?
Anything else?
Other comments, collaborators, etc.
This PR Closes #<issue_number>