Skip to content

REF-98 Prepare release 3.1.0 - #109

Merged
thomasnymand merged 2 commits into
mainfrom
feature/REF-98-release-3.1.0
Nov 2, 2026
Merged

thomasnymand merged 2 commits into
mainfrom
feature/REF-98-release-3.1.0

Conversation

@thomasnymand

Copy link
Copy Markdown
Collaborator

Prepares the 3.1.0 release of dk.nita.saml20, dk.nita.saml20.ext.audit.log4net and dk.nita.saml20.ext.sessionstore.sqlserver.

Release notes: RELEASE_NOTES.md has a 3.1.0 entry covering #96 to #108, with a section "Upgrading from 3.0.x" listing the changes integrators may have to act on.

Licence: a LICENSE file with the MPL 1.1 text, which the packages have always declared.

Package metadata: the nuspecs point to this repository (project and repository URL) and to RELEASE_NOTES.md. The core package's readme.txt no longer refers to digitaliser.dk.

Release workflow (.github/workflows/release.yml):

  • A version tag on main, without a v as before (3.1.0, since the assembly version is read from the tag), builds, runs the tests and packs the three packages with symbol packages.
  • The publish job runs in the nuget environment, so a reviewer must approve it, and pushes to nuget.org by Trusted Publishing; no API key is stored.
  • Running it by hand only builds the packages (version 0.0.0-ci.N) as an artifact.

Other: build/BuildPackages.ps1 packs the same three packages locally and no longer pushes. developernotes.md describes the release procedure and the one-time setup; the integration-test link points to NemLog-in's current document.

Checked: packed locally in Windows: all three packages carry the version, licence, URLs and release notes; the log4net package depends on log4net 3.5.0 and both extensions on the same dk.nita.saml20 version; symbol packages are produced.

One-time setup before the first tagged release (a nuget.org owner of the packages):

  • On nuget.org, a Trusted Publishing policy for digst/OIOSAML.Net, workflow release.yml, environment nuget.
  • In this repository, the nuget environment with required reviewers, and the variable NUGET_USER (the nuget.org account that owns the policy).

…a and a Release workflow with Trusted Publishing

- RELEASE_NOTES.md: 3.1.0 with "Upgrading from 3.0.x".
- LICENSE: the MPL 1.1 text, as the packages have always declared.
- nuspec: project and repository URL on GitHub, release notes link to
  RELEASE_NOTES.md; package readme updated.
- .github/workflows/release.yml: a version tag on main builds, tests and packs
  the three packages and publishes them to nuget.org by Trusted Publishing
  after approval; a run by hand only builds them.
- build/BuildPackages.ps1 builds the same packages locally; the version
  parameter that had no effect is gone.
- developernotes.md: the release procedure; readme links.
@thomasnymand
thomasnymand merged commit 63ffd2a into main Nov 2, 2026
2 checks passed
@thomasnymand
thomasnymand deleted the feature/REF-98-release-3.1.0 branch November 2, 2026 09:42
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.

1 participant