Release of the admin with a preview of its packages (A-47)
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 20/100
Piste de recherche
Start with docs/planning/admin-technical-spec.md sections 2.8, 6 and 10.8, then trace the named release workflow, admin options, hosting package project and release documentation. The acceptance checklist defines completion across package publishing, default hosting behavior, API checks, version constraints, startup reporting and documentation; the issue says this work depends on every other A7 issue and includes maintainer-controlled release steps.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Problem
Every release builds the admin and holds it back, in four places:
- The packages. The
Publishworkflow packs every package and then removesFluentCMS.Admin*before anything is pushed, with the note "A-47 removes this step" (.github/workflows/publish.yml, lines 205 to 208). The pattern does not match the halves,FluentCMS.Plugins.*.Admin, which is a fault of its own until this issue (see the notes of the milestone). - The image.
FluentCms:Admin:Enabledis false unless set (admin/src/FluentCMS.Admin.Hosting/AdminOptions.cs, lines 13 and 14), so the image serves no admin until an operator turns it on. Section 6.1 has A-47 make it true. - The words. The README says the admin is not part of the preview (line 20), and
docs/releasing.mdthat the admin packages are left out of a release (line 38). - The static build is attached to no release (A-43 adds it).
Three things are open about what is released:
- Which packages promise what.
FluentCMS.Admin.AbstractionsandFluentCMS.Admin.Componentstrack their public surface (section 2.8).FluentCMS.AdminandFluentCMS.Admin.Hostinghave the entry points a team'sProgram.cscalls (AddFluentCmsAdmin,AdminApp,AddAdmin,MapFluentCmsAdmin,AdminOptions) and no public API file. Row 11.11 asks for a published policy. - The hosting package reads Core's internals.
FluentCMS.CorenamesFluentCMS.Admin.HostinginInternalsVisibleTo(src/FluentCMS.Core/FluentCMS.Core.csproj, line 37), and the package uses at least six internal types of Core (FluentCmsSurfaceMetadata,FluentCmsEndpointMetadata,ContentSecurityPolicyMetadata,ApiPipelineState,HostErrorCodes,FluentCmsOptions), so it works with the one build of Core it was compiled with and fails at run time with another (#3178). - A client the host configures itself is not checked. With a secret, or without the scopes, the host starts and
config.jsonstill lists the five scopes, so the sign-in fails in the browser with no word from the host (#3178). On by default, every operator who configured that client meets it.
Proposal
- The release pushes the admin. The step that removes the packages goes; the twelve admin packages (
FluentCMS.Admin,.Abstractions,.Components,.RichText,.Administration,.Hostingand the six halves) are pushed with their symbols, and the zip of A-43 is attached.eng/check-packages.csalready checks them in thePackjob. - On by default.
FluentCms:Admin:Enabledis true unless set to false.docs/docker.md,docs/host-configuration.md,.env.exampleand the notes say how to turn it off and what it needs (FluentCms:PublicOrigin, https), and the lines that turn it on in theComposejob and in the end-to-end harness go. - The promise.
FluentCMS.AdminandFluentCMS.Admin.Hostingget the public API analyzer and their two files, with every entry unshipped, as a preview keeps them.docs/releasing.mdlists the admin packages in each step that names packages, and says which carry the promise of row 11.11 (the contract and the wrapped set), whatAdminRangeand the manifest version give a half built for one minor, and that the other packages are a preview without one. - The hosting package and Core. Until Core has a public seam (see the notes of the milestone), the package depends on the exact version of
FluentCMS.Coreit was built with, so that a mismatch is refused at restore and not met at run time. - A configured client is named at start. While the admin is on, a client
fluentcms-adminthat has a secret, or lacks a scope or the redirect URI of the served admin, is reported in the startup report with what is missing. No new refusal in a preview. - The notes and the README. The notes of the release that is open when A7 ends get the section of the admin: the three distributions, how to turn it off, the packages as a preview, the supported browsers, English alone, the exceptions of the audit (A-42) and what is known to be missing. The README shows how to open
/admin. - A rehearsal. A manual run of
Publishlists the admin packages and the zip. After the tag,Composeand the end-to-end job of A-45 are run by hand with the published image.
Acceptance
- A dry run of
Publishlists the twelve admin packages with their symbols andfluentcms-admin-{version}.zip, and no step leaves a package out - The image with nothing set about the admin serves it at
/admin, andFluentCms__Admin__Enabled=falseanswers 404 there and registers no client -
FluentCMS.AdminandFluentCMS.Admin.Hostingfail the build on a public member that is in neither of their files - The packed
FluentCMS.Admin.Hostingdepends onFluentCMS.Coreat its exact version - A configured client
fluentcms-adminwith a secret is named in the startup report -
docs/releasing.md, the README and the notes of the release say what ships, and the first two no longer say that the admin is held back - The
Fresh machinejobs pass with the admin packages from the feed - The items of #3178 on the public seam and on the configured client are ticked or point at the issue that keeps them
Design: docs/planning/admin-technical-spec.md, sections 2.8, 6 and 10.8 (A-47). Rows 10.2, 11.11. Takes two items of #3178. Needs every other issue of A7. The version, the tag and the approval of the release are the maintainer's. Size: M.
- Langage dominant
- C#
- Étoiles
- 567
- Forks
- 107
- Merge moyen
- 1 h 19 min
- PR mergées (30 j)
- 353
Préparer son environnement
- Fournit un Dockerfile ou un fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de fluentcms/FluentCMS
-
area:localization plugin type:bug
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 1 jour
-
area:storage type:bug
Difficulté 4/5 3-5 jours Accessibilité débutants 48/100
Les mainteneurs répondent en général sous 1 jour
-
area:testing type:bug
Difficulté 3/5 1-2 jours Accessibilité débutants 72/100
Les mainteneurs répondent en général sous 1 jour
-
area:api area:publishing type:feature
Difficulté 4/5 3-5 jours Accessibilité débutants 55/100
fluentcms/FluentCMS#3473 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
area:storage plugin type:bug
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 35/100
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de fluentcms/FluentCMS
Issues similaires
-
[Bug]: Threading.Analyzers 0.7.79 does not load on the .NET 10 SDK (CS9057), CHT rules silently offOuvertebug regression threading
Difficulté 2/5 1-3 heures Accessibilité débutants 74/100
CryptoHives/Foundation#362 ·
Les mainteneurs répondent en général sous 1 jour
-
[Bug]: 本地歌词翻译显示错误Ouvertebug need-triage
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100
Fervent-Tempo/AF-Media-Bar#321 ·
-
a-corriger documentation
Difficulté 1/5 Moins d'une heure Accessibilité débutants 87/100
christian-raj/S-Aloha#345 ·
-
bug 要トリアージ
Difficulté 2/5 1-3 heures Accessibilité débutants 64/100
Les mainteneurs répondent en général sous 1 jour
-
worldInstancedOccluderNode reads its appendix count as one byte, but it is a VLQPeut-être pris @spuddeh l’a pris aujourd’hui. Ouverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 1 jour