Skip to content

Rename NuGet packages to AutoGuru.EntityFrameworkCore.Triggered#214

Closed
anthony-keller wants to merge 2 commits intoEFNext:v3from
autoguru-au:feature/autoguru-nuget-package-rename
Closed

Rename NuGet packages to AutoGuru.EntityFrameworkCore.Triggered#214
anthony-keller wants to merge 2 commits intoEFNext:v3from
autoguru-au:feature/autoguru-nuget-package-rename

Conversation

@anthony-keller
Copy link

Summary

  • Add AutoGuru. prefix to all NuGet package IDs via PackageId property in src/Directory.Build.props
  • Update package metadata (Authors, RepositoryUrl, PackageProjectUrl) to point to autoguru-au fork
  • Simplify CI workflows to v3-only builds, update GitHub Actions to v4

Test plan

  • dotnet build EntityFrameworkCore.Triggered.sln — 0 errors
  • dotnet test EntityFrameworkCore.Triggered.sln — 241/241 tests passed
  • dotnet pack -c Release -p:PackageVersion=3.4.0-test — all 5 .nupkg files named AutoGuru.EntityFrameworkCore.Triggered*.nupkg
  • After merge: add NUGET_KEY secret, create GitHub Release with tag v3.4.0 to trigger deployment

🤖 Generated with Claude Code

anthony-keller and others added 2 commits March 8, 2026 11:45
Add CLAUDE.md to provide guidance for Claude Code when working with this repository. The file documents project overview, build and test commands, multi-version build system (V1/V2/V3), global build settings, architecture and core flow of the trigger library, key internal types, and test project layout. Intended as a quick reference for building, testing, and understanding trigger execution and project structure.
Add AutoGuru. prefix to all package IDs via src/Directory.Build.props,
update package metadata to point to the autoguru-au fork, and simplify
CI workflows to v3-only with updated GitHub Actions versions.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@anthony-keller
Copy link
Author

Opened against wrong repo, re-creating against autoguru-au fork.

@anthony-keller anthony-keller deleted the feature/autoguru-nuget-package-rename branch March 10, 2026 04:58
@PhenX
Copy link
Member

PhenX commented Mar 21, 2026

Hi @anthony-keller would you mind contributing to the original project ? we'd like to revive it

@anthony-keller
Copy link
Author

Hi @anthony-keller would you mind contributing to the original project ? we'd like to revive it

I have a contribution for one of our fixes. It hasn't seen any action.

We've not contributed our upgrade to .net 9 yet.

We're happy to go back to the original if it's revived. We had an urgent issue we were trying to resolve so had to fork.

@PhenX
Copy link
Member

PhenX commented Mar 21, 2026

Great! We'll be happy to integrate it if you make a pull request.
We'll work on ef core 9 and 10 support too.

@anthony-keller
Copy link
Author

Great! We'll be happy to integrate it if you make a pull request. We'll work on ef core 9 and 10 support too.

Here is the original PR - #213

Would you prefer if I raise and issue and fresh PR for this? I'll be able to do that sometime over the next 1-2 days?

@PhenX
Copy link
Member

PhenX commented Mar 21, 2026

Let's reopen it, I'll see if it's ok

@anthony-keller
Copy link
Author

Let's reopen it, I'll see if it's ok

Okay. We have been running with that + an upgrade to .NET 9 for a couple of weeks now without any issues. So far that's all we've changed, however, we do have a list of other potential improvements suggested by Claude. Happy to share those too if you like?

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.

2 participants