Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Release v1.4.0

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp, github-actions, linux, macos, sqlite
Domain
desktop, devops, release

Research direction

Start by checking the milestone’s open issues and its “Done when” criteria; this release depends on both being complete. Follow the Directory.Build.props version bump through the three “Build and test” jobs, then inspect the merged main commit before tagging v1.4.0. Verify the draft AppImage in WSLg and the listed update checks across Windows, Ubuntu and macOS; done means the release is published and ROADMAP.md records it under Shipped.

Written by the indexing model from the issue text.

Description

Release 1.4.0 once every other issue in this milestone is closed and the milestone's "Done when" holds.

What to do

  1. A pull request titled chore(release): 1.4.0 bumps the version in Directory.Build.props. It merges like any other change, once the three "Build and test" jobs pass.
  2. Tag the merged commit on main as v1.4.0 and push the tag. v* tags can't be moved or deleted, so check the commit first. The release workflow packs every platform, runs the smoke tests and opens a draft release.
  3. Before publishing, open the draft's AppImage in WSLg with scratch folders and try the milestone's new features there.
  4. The owner publishes the draft. Installed copies only see published releases, and winget.yml submits it to winget.
  5. After publishing:
    • a portable 1.3.0 on Windows finds 1.4.0 in Settings › Updates, updates, restarts into it and keeps its library, and its bundled prompuff moves to 1.4.0 too
    • update-check.yml, run by hand, finds 1.4.0 from 1.3.0 on Windows, Ubuntu and macOS
  6. A docs: record the 1.4.0 release pull request adds the row to Shipped in ROADMAP.md and a "Checked for 1.4.0" decision with what was checked by hand.

Done when

  • v1.4.0 is published on the releases page, and the checks above passed.
  • ROADMAP.md lists it under Shipped.
Dominant language
C#
Stars
0
Forks
1
Avg merge
1h 21m
Merged PRs (30d)
22

Getting set up

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 hazeliscoding/prompuff

All issues in hazeliscoding/prompuff

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.