Skip to content

Migrate to .NET 8 (dotnet8_minimal_awssdk → main)#4

Draft
Faisal-Bahoo wants to merge 18 commits into
mainfrom
dotnet8_minimal_awssdk
Draft

Migrate to .NET 8 (dotnet8_minimal_awssdk → main)#4
Faisal-Bahoo wants to merge 18 commits into
mainfrom
dotnet8_minimal_awssdk

Conversation

@Faisal-Bahoo

Copy link
Copy Markdown

Summary

  • Migrates the LambdaSharp tool and all modules from .NET 3.1/6.0 to .NET 8
  • Bumps version to 0.8.5.1
  • Adds MindTouch-internal changes: Rollbar project setup, CodeArtifact NuGet push scripts
  • Adds .NET 8 function templates (net80/) for lash new

Why

LambdaSharpConfig.json in Deki now targets version 0.8.5.1. The CD pipeline (update-lambda-sharp.sh) calls lash publish LambdaSharp.S3.IO:0.8.5.1@lambdasharp during tier upgrades — this requires 0.8.5.1 artifacts to exist in the s3://lambdasharp/ bucket. The upstream public bucket tops out at 0.8.4.1. Merging this branch and running Scripts/update-release.sh will publish 0.8.5.1 artifacts so all tiers can resolve them without manual seeding.

Known issues to resolve before merging

  • dotnet-core.yml CI still targets .NET 3.1 and 6.0 — needs updating to .NET 8 so CI passes on this branch
  • Scripts/update-release.sh should be wired into CI as a publish step (triggered on merge to main) — see Deki #38135
  • .idea/ IDE config files included in diff — consider adding to .gitignore before merge

Test plan

  • CI passes with .NET 8 after workflow is updated
  • Scripts/update-release.sh runs successfully and 0.8.5.1 artifacts appear in s3://lambdasharp/
  • lash publish LambdaSharp.S3.IO:0.8.5.1@lambdasharp resolves correctly in a non-alpha tier

🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants