Skip to content

Update to Deno 2.7.1 and remove unconditional Temporal unstable requirements#588

Merged
dahlia merged 2 commits intofedify-dev:mainfrom
dahlia:main
Feb 26, 2026
Merged

Update to Deno 2.7.1 and remove unconditional Temporal unstable requirements#588
dahlia merged 2 commits intofedify-dev:mainfrom
dahlia:main

Conversation

@dahlia
Copy link
Member

@dahlia dahlia commented Feb 26, 2026

Summary

This PR updates the repository to use Deno 2.7.1 and removes unconditional Temporal unstable-flag requirements where they are no longer needed.

  • Bump pinned Deno version to 2.7.1 in mise.toml
  • Update CI Deno setup version to 2.7.1
  • Remove --unstable-temporal from root check tasks/config
  • Remove root unstable.temporal usage
  • Update @fedify/init generation logic:
    • Add "temporal" to unstable only when installed Deno is < 2.7.0
    • Omit unstable field when no unstable features are required
  • Update docs/README:
    • Default Deno commands no longer include --unstable-temporal
    • Clarify that Deno < 2.7.0 still needs --unstable-temporal or unstable.temporal

Why

Since the Temporal API is stabilized in Deno 2.7, the previous unconditional unstable Temporal configuration is no longer necessary on modern Deno versions.

Validation

  • mise run check:types passed
  • deno check packages/init/src/action/configs.ts passed

Notes

This keeps backward compatibility for users on Deno versions earlier than 2.7.0 through conditional handling in fedify init.

Bumped the pinned Deno version to 2.7.1 in mise and the shared
GitHub Actions setup.

Removed unconditional --unstable-temporal usage from root check tasks
and configuration now that Temporal is stable in Deno 2.7.

Updated fedify init's Deno config generation so temporal is added to
unstable only on Deno versions earlier than 2.7.0, and omitted when no
unstable flags are required.

Refreshed installation and tutorial documentation to remove
--unstable-temporal from default commands and clarify the compatibility
note for Deno versions below 2.7.0.

Added a changelog entry describing the runtime bump and Temporal
compatibility updates.

Co-Authored-By: Codex <codex@openai.com>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @dahlia, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request modernizes the project's Deno environment by upgrading to version 2.7.1 and adapting to the stabilization of the Temporal API. The changes streamline configurations by removing unnecessary unstable flags and introduce intelligent version-aware handling for the Temporal API in project initialization, ensuring compatibility across different Deno versions while leveraging the latest stable features.

Highlights

  • Deno Version Update: The project's pinned Deno version has been updated to 2.7.1 across mise.toml and CI configurations, aligning with the latest stable release.
  • Temporal API Stabilization: Unconditional requirements for the --unstable-temporal flag and the temporal entry in deno.json's unstable array have been removed, as the Temporal API is now stable in Deno 2.7.0.
  • Conditional Unstable Flag Handling: The @fedify/init generation logic has been enhanced to conditionally add "temporal" to the unstable field only when the installed Deno version is older than 2.7.0, ensuring backward compatibility.
  • Documentation Updates: Documentation and READMEs have been updated to reflect the removal of --unstable-temporal from default Deno commands and to clarify the conditional requirement for older Deno versions.
Changelog
  • CHANGES.md
    • Changed fedify init to add "temporal" to deno.json's "unstable" field only when the installed Deno version is earlier than 2.7.0.
    • fedify init now omits the "unstable" field entirely when no unstable feature is required for the generated Deno project.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@issues-auto-labeler issues-auto-labeler bot added component/build Build system and packaging component/ci CI/CD workflows and GitHub Actions component/cli CLI tools related labels Feb 26, 2026
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates Deno to version 2.7.1 and removes the now-unnecessary --unstable-temporal flag. The changes are consistent across configuration, documentation, and CI files. A key improvement is the new logic in @fedify/init to conditionally add the unstable flag based on the detected Deno version, ensuring backward compatibility. The implementation is robust, but I have one suggestion to improve debuggability in the version detection logic.

Add debug logging in the Deno version fallback path for fedify init so
errors from `deno --version` are no longer silently swallowed.

The existing `null` fallback behavior remains unchanged, but unexpected
runtime or permission issues are now diagnosable during troubleshooting.

fedify-dev#588 (comment)

Co-Authored-By: Codex <codex@openai.com>
@codecov
Copy link

codecov bot commented Feb 26, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.
see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dahlia dahlia merged commit 1373184 into fedify-dev:main Feb 26, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component/build Build system and packaging component/ci CI/CD workflows and GitHub Actions component/cli CLI tools related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants