Repository navigation
docs: pin hyperstructure/fctl@0840d6cfec52 - #25
Merged
Merged
Conversation
fctl.sh still showed fctl's docs from 8e4bc48, from before two-factor sign-in and passkeys. The CI run that would have pinned them failed on a flaky test, and the release commit after it changed no docs.
This was referenced Oct 19, 2026
kalaspuff
approved these changes
Oct 19, 2026
kalaspuff
deleted the
fctl/51-the-ci-workflow-for-fctl-seems-to-have-f
branch
October 19, 2026 19:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fctl.sh still shows fctl's docs from hyperstructure/fctl@8e4bc48, from before two-factor sign-in and passkeys (hyperstructure/fctl#103, hyperstructure/fctl#104), which v0.8.0 shipped. None of its docs pages mention either.
fctl's CI pins this file when a push to its
mainchangesdocs/. The push that changed them, hyperstructure/fctl@65dcbe1, failedcargo xtask checkon a flaky test, so its pin was skipped. The release commit after it changed no docs, so its run had nothing to pin. This pins that release commit, hyperstructure/fctl@0840d6c (v0.8.0), whose docs are those of 65dcbe1.How I checked it:
npm run buildrendered the 8 docs pages from 0840d6c. Two-factor sign-in and passkeys now appear in Getting started, The CLI, Self-hosting, Architecture and Security.npm testpasses, andnpm run checkshows the same 2 warnings as onmain.Refs hyperstructure/fctl#105 (why the pin was missed) and hyperstructure/fctl#106 (the flaky tests).
Session: https://app.fctl.sh/s/ses_01M5AFQJTX6FENQJJZWRD5AP5K