docs: propose automatic Deno version bumps#2
Draft
TomChv wants to merge 1 commit into
Draft
Conversation
Keep the module's default Deno version current via a Dagger-native bump function (.dagger/modules/maintenance) that rewrites deno.dang + README and returns a Changeset, driven by a scheduled workflow using dagger-for-github (engine version sourced from dagger-module.toml). Verification is the module's own e2e suite, which runs on the default version and gates both image availability and tests. README kept in sync; no auto-merge; not Dependabot (the default is a Dang source literal no ecosystem parses). Signed-off-by: Tom Chauveau <tom@dagger.io>
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
1 participant
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.
Draft — design proposal only. Not implementing yet; this PR just tracks the plan.
Adds
designs/auto-version-bump.md: keep the module'sdefault Deno version current via a Dagger-native bump function (a
.dagger/modules/maintenancemodule:latestDenoVersionfromgit(denoland/deno).tags,bumpDenoVersion → Changesetrewritingdeno.dang+README.md) driven by a scheduleddagger-for-githubworkflow. Verification is the module's own e2e suite (runs on thedefault version, so it gates both image availability and tests). Rolling PR, no auto-merge,
Dagger Cloud traces, engine version sourced from
dagger-module.toml. Not Dependabot — thedefault is a Dang source literal no ecosystem parses.
Depends on #1
This branch is stacked on top of
feat/add-deno-module(#1), so this PR is based onthat branch and its diff is just the proposal doc. Merge #1 first; I'll retarget this to
mainonce #1 lands.Implementation (the
maintenancemodule +.github/workflows/bump-deno-version.yml) isdeliberately deferred — this stays a tracking placeholder for now.