Skip to content

docs(changelog): note Billing config key rename (GraceWindowDays -> GracePeriodDays) #230

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
marcelo-maciel wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(changelog): note Billing config key rename (GraceWindowDays -> GracePeriodDays) #230

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion src/content/docs/changelog/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: Overview
lastUpdated: 2026-06-20
lastUpdated: 2026-06-24
description: Release notes and version history for fullstackhero.
sidebar:
order: 1
Expand All @@ -11,6 +11,10 @@ seo:

Notable changes to the kit, newest first.

## 2026-06-24

- **Config: the tenant billing grace-period setting was renamed `Billing:GraceWindowDays` → `Billing:GracePeriodDays` (breaking).** The option (bound in both `TenantBillingOptions` and Identity's `TenantGraceOptions`) is now named consistently with the "grace period" term used everywhere else in the kit; the default of 7 days is unchanged. Deployments that set `Billing:GraceWindowDays` (env `Billing__GraceWindowDays`) must rename the key to `Billing:GracePeriodDays`, otherwise the override is silently ignored and the default applies. No public contract change — the `GraceEndsUtc` tenant-status and integration-event fields are untouched. See PR [#1313](https://github.com/fullstackhero/dotnet-starter-kit/pull/1313).

## 2026-06-20

- **The `fsh` CLI and `dotnet new` template are now on NuGet as stable `10.0.0`.** The two distribution packages that 10.0.0 had been waiting on have shipped: `FullStackHero.CLI` (install with `dotnet tool install -g FullStackHero.CLI` — no more `--prerelease`) and `FullStackHero.NET.StarterKit` (`dotnet new install FullStackHero.NET.StarterKit`). Because `fsh new` scaffolds *from* that template, the one-command flow is now end-to-end: `dotnet tool install -g FullStackHero.CLI && fsh new MyApp` produces a fully renamed project — unique JWT signing key, generated Docker secrets, `npm install` run, initial commit on `main`. The [Install](/docs/getting-started/install/) and [CLI](/docs/cli/) pages now lead with the CLI as the recommended path; `git clone` and the GitHub template remain available for reading the source or zero-install runs. See the [10.0.0 release](https://github.com/fullstackhero/dotnet-starter-kit/releases/tag/10.0.0).
Expand Down