fix(deps): root package pins @flisk-sh/flisk 1.4.5, far behind the current 1.4.65

Open
  • Is something wrong?
#40 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
bun, github-actions
Domain
build-system, ci-cd

Research direction

Start at the root package.json and the flisk:project, flisk:dry-run and flisk:up scripts that use the @flisk-sh/flisk pin; reproduce with bun install then bun run flisk:up and flisk --version. Then read the existing CI workflow and any dependency-bot config to see where a job that starts the stack against the latest release would go. Done means the pin is on 1.4.65, CI proves the latest CLI starts, a bot or scheduled job keeps it fresh, and the README names the supported version.

Written by the indexing model from the issue text.

Description

area: cli bug chore ci dependencies developer-experience difficulty: easy docs dx first-run flisk-cli good first issue help wanted maintenance onboarding priority: P2 quality version-drift

Problem

The root package of this repo pins @flisk-sh/flisk to 1.4.5, and its scripts (flisk:project, flisk:dry-run, flisk:up) run that version. The current release is far newer (1.4.65), so a new user who follows the README runs a CLI that is many releases old and misses every fix since, including startup and routing fixes.

Reproduce:

  1. Clone, bun install at the root, bun run flisk:up.
  2. flisk --version prints 1.4.5. npm view @flisk-sh/flisk version prints a much newer one.

Expected: the pin follows the latest release, or the project uses an unpinned or range version and CI proves it still starts.

Root Cause Analysis

The version was pinned once for a reproducible demo and never bumped. No automated update (a dependency bot rule or a scheduled job) covers the root package, and CI does not run the project against the latest CLI, so drift is invisible.

TDD Fix Plan

  1. RED: Write a CI check that starts the stack with the pinned version and with the latest release and fails if the latest does not start.
    GREEN: Bump the pin to the current release.

  2. RED: Write a check that fails when the pin is more than a set number of releases behind.
    GREEN: Add a dependency-bot entry for the root package.

REFACTOR: Mention the supported CLI version in the README.

Acceptance Criteria

  • The root package uses a current CLI version
  • CI starts the project with the latest CLI
  • A bot or scheduled job keeps the pin fresh
  • All new tests pass
  • Existing tests still pass
Dominant language
Shell
Stars
3
Forks
0
Avg merge
5m
Merged PRs (30d)
6

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flisk-sh/flisk-example

All issues in flisk-sh/flisk-example

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.