Upgrade the pinned features #1

Open
forgejo-actions wants to merge 1 commit from splent/feature-upgrades into main

The pinned features have newer releases that install together and keep the product valid in its line. Review the plan below, merge, and publish with splent product:release.


  feature:upgrade  splent_marketplace_app

  Reading 12 features from the forge and from PyPI...
  The forge could not be read for splent_feature_session_filesystem (splent-io/splent_feature_session_filesystem does not exist or this token cannot see it).
  The forge could not be read for splent_feature_configurator (splent-io/splent_feature_configurator does not exist or this token cannot see it).
  The forge could not be read for splent_feature_skin_store (splent-io/splent_feature_skin_store does not exist or this token cannot see it).
  The forge could not be read for splent_feature_signup (splent-io/splent_feature_signup does not exist or this token cannot see it).
  The forge could not be read for splent_feature_marketplace (splent-io/splent_feature_marketplace does not exist or this token cannot see it).
  The forge could not be read for splent_feature_apikeys (splent-io/splent_feature_apikeys does not exist or this token cannot see it).
  The forge could not be read for splent_feature_spl_registry (splent-io/splent_feature_spl_registry does not exist or this token cannot see it).
  The forge could not be read for splent_feature_autodeploy (splent-io/splent_feature_autodeploy does not exist or this token cannot see it).
  The forge could not be read for splent_feature_settings (splent-io/splent_feature_settings does not exist or this token cannot see it).
  The forge could not be read for splent_feature_theme (splent-io/splent_feature_theme does not exist or this token cannot see it).
  The forge could not be read for splent_feature_auth (splent-io/splent_feature_auth does not exist or this token cannot see it).
  The forge could not be read for splent_feature_admin (splent-io/splent_feature_admin does not exist or this token cannot see it).
  Asking pip for the newest versions that install together, with splent_framework and splent_cli==1.49.0...

    Feature             Pinned   Planned
    session_filesystem  v1.2.0   v1.2.0   up to date
    configurator        v0.3.0   v0.3.0   up to date
    skin_store          v0.3.0   v0.3.0   up to date
    signup              v0.2.0   v0.4.1   upgrade
    marketplace         v0.4.0   v0.4.0   up to date
    apikeys             v0.2.1   v0.10.0  upgrade, adds 2 migrations
    spl_registry        v0.5.0   v0.5.0   up to date
    autodeploy          v0.1.2   v0.4.0   upgrade
    settings            v0.4.3   v0.5.1   upgrade
    theme               v0.13.4  v0.16.0  upgrade
    auth                v1.19.4  v1.27.0  upgrade, adds 6 migrations
    admin               v1.6.1   v1.9.0   upgrade

  Migrations db:upgrade will apply
    apikeys  apikeys0002_lifecycle  Why a token was revoked, and which expiry notice its owner was sent.
    apikeys  apikeys0003_resources  What a token is limited to (AP-4).
    auth     auth0004_account_state  Verified apart from switched off, a canonical address, and session versions.
    auth     auth0005_one_time_tokens  One-time tokens for the links auth's features mail (see tokens.py).
    auth     auth0006_account_origin  Where an account came from, how its address was proved, and whether its
    auth     auth0007_service_account  Whether a program signs in with the account rather than a person.
    auth     auth0008_must_reset_password  Whether the owner has to choose a new password before signing in again.
    auth     auth0009_email_collation  The address as typed is compared exactly, in the database too (DM-15, ID-2).

  pip resolves these 12 features together with splent_framework 1.29.0 and splent_cli 1.49.0.
  7 features to upgrade.

  Applying
    cache    cloning splent_io/splent_feature_signup@v0.4.1
    cache    cloning splent_io/splent_feature_apikeys@v0.10.0
    cache    cloning splent_io/splent_feature_autodeploy@v0.4.0
    cache    cloning splent_io/splent_feature_settings@v0.5.1
    cache    cloning splent_io/splent_feature_theme@v0.16.0
    cache    cloning splent_io/splent_feature_auth@v1.27.0
    cache    cloning splent_io/splent_feature_admin@v1.9.0
    pin      signup v0.2.0 to v0.4.1
    pin      apikeys v0.2.1 to v0.10.0
    pin      autodeploy v0.1.2 to v0.4.0
    pin      settings v0.4.3 to v0.5.1
    pin      theme v0.13.4 to v0.16.0
    pin      auth v1.19.4 to v1.27.0
    pin      admin v1.6.1 to v1.9.0
  pyproject.toml pins the new versions. Its comments and layout are untouched.

  Validating the product
    config      passed
    compat      passed
    refinement  passed

  Next steps
    splent product:derive    installs the new versions and restarts the product
    splent product:resolve   only refreshes the cache and the links
    splent db:upgrade        applies the 8 new migrations listed above

  Updated deploy, splent.contracts.json, docker/frontend.lock.json for the pins, as product:build --no-image writes them. Commit them with the pins.

The pinned features have newer releases that install together and keep the product valid in its line. Review the plan below, merge, and publish with splent product:release. ``` feature:upgrade splent_marketplace_app Reading 12 features from the forge and from PyPI... The forge could not be read for splent_feature_session_filesystem (splent-io/splent_feature_session_filesystem does not exist or this token cannot see it). The forge could not be read for splent_feature_configurator (splent-io/splent_feature_configurator does not exist or this token cannot see it). The forge could not be read for splent_feature_skin_store (splent-io/splent_feature_skin_store does not exist or this token cannot see it). The forge could not be read for splent_feature_signup (splent-io/splent_feature_signup does not exist or this token cannot see it). The forge could not be read for splent_feature_marketplace (splent-io/splent_feature_marketplace does not exist or this token cannot see it). The forge could not be read for splent_feature_apikeys (splent-io/splent_feature_apikeys does not exist or this token cannot see it). The forge could not be read for splent_feature_spl_registry (splent-io/splent_feature_spl_registry does not exist or this token cannot see it). The forge could not be read for splent_feature_autodeploy (splent-io/splent_feature_autodeploy does not exist or this token cannot see it). The forge could not be read for splent_feature_settings (splent-io/splent_feature_settings does not exist or this token cannot see it). The forge could not be read for splent_feature_theme (splent-io/splent_feature_theme does not exist or this token cannot see it). The forge could not be read for splent_feature_auth (splent-io/splent_feature_auth does not exist or this token cannot see it). The forge could not be read for splent_feature_admin (splent-io/splent_feature_admin does not exist or this token cannot see it). Asking pip for the newest versions that install together, with splent_framework and splent_cli==1.49.0... Feature Pinned Planned session_filesystem v1.2.0 v1.2.0 up to date configurator v0.3.0 v0.3.0 up to date skin_store v0.3.0 v0.3.0 up to date signup v0.2.0 v0.4.1 upgrade marketplace v0.4.0 v0.4.0 up to date apikeys v0.2.1 v0.10.0 upgrade, adds 2 migrations spl_registry v0.5.0 v0.5.0 up to date autodeploy v0.1.2 v0.4.0 upgrade settings v0.4.3 v0.5.1 upgrade theme v0.13.4 v0.16.0 upgrade auth v1.19.4 v1.27.0 upgrade, adds 6 migrations admin v1.6.1 v1.9.0 upgrade Migrations db:upgrade will apply apikeys apikeys0002_lifecycle Why a token was revoked, and which expiry notice its owner was sent. apikeys apikeys0003_resources What a token is limited to (AP-4). auth auth0004_account_state Verified apart from switched off, a canonical address, and session versions. auth auth0005_one_time_tokens One-time tokens for the links auth's features mail (see tokens.py). auth auth0006_account_origin Where an account came from, how its address was proved, and whether its auth auth0007_service_account Whether a program signs in with the account rather than a person. auth auth0008_must_reset_password Whether the owner has to choose a new password before signing in again. auth auth0009_email_collation The address as typed is compared exactly, in the database too (DM-15, ID-2). pip resolves these 12 features together with splent_framework 1.29.0 and splent_cli 1.49.0. 7 features to upgrade. Applying cache cloning splent_io/splent_feature_signup@v0.4.1 cache cloning splent_io/splent_feature_apikeys@v0.10.0 cache cloning splent_io/splent_feature_autodeploy@v0.4.0 cache cloning splent_io/splent_feature_settings@v0.5.1 cache cloning splent_io/splent_feature_theme@v0.16.0 cache cloning splent_io/splent_feature_auth@v1.27.0 cache cloning splent_io/splent_feature_admin@v1.9.0 pin signup v0.2.0 to v0.4.1 pin apikeys v0.2.1 to v0.10.0 pin autodeploy v0.1.2 to v0.4.0 pin settings v0.4.3 to v0.5.1 pin theme v0.13.4 to v0.16.0 pin auth v1.19.4 to v1.27.0 pin admin v1.6.1 to v1.9.0 pyproject.toml pins the new versions. Its comments and layout are untouched. Validating the product config passed compat passed refinement passed Next steps splent product:derive installs the new versions and restarts the product splent product:resolve only refreshes the cache and the links splent db:upgrade applies the 8 new migrations listed above Updated deploy, splent.contracts.json, docker/frontend.lock.json for the pins, as product:build --no-image writes them. Commit them with the pins. ```
forgejo-actions force-pushed splent/feature-upgrades from 114d9df95c to 2eaae1f242 2026-11-02 07:10:41 +01:00 Compare
This pull request has changes conflicting with the target branch.
  • pyproject.toml
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin splent/feature-upgrades:splent/feature-upgrades
git switch splent/feature-upgrades

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff splent/feature-upgrades
git switch splent/feature-upgrades
git rebase main
git switch main
git merge --ff-only splent/feature-upgrades
git switch splent/feature-upgrades
git rebase main
git switch main
git merge --no-ff splent/feature-upgrades
git switch main
git merge --squash splent/feature-upgrades
git switch main
git merge --ff-only splent/feature-upgrades
git switch main
git merge splent/feature-upgrades
git push origin main
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
splent-io/splent_marketplace_app!1
No description provided.