Skip to content

Simplify release and back-to-dev processes #4860

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

submarcos
Copy link
Member

@submarcos submarcos commented Aug 1, 2025

Description

Make easier release and back-to-dev processes

make release version=x.yyy.z

  • update VERSION file content with x.yyy.z
  • update debian/changelog with x.yyy.z version entry (use support geotrek mail to identify maintainer)
  • update docs/changelog.rst '+dev (XXXX-XX-XX)' with specified version and current date.

make back_to_dev version=x.yyy.z

  • update VERSION file content with x.yyy.z+dev
  • update debian/changelog with x.yyy.z+dev UNRELEASED version entry (use support geotrek mail to identify maintainer)
  • update docs/changelog.rst, add new entry with +dev and XXXX-XX-XX

Related Issue

Checklist

  • I have followed the guidelines in our Contributing document
  • My code respects the Definition of done available in the Development section of the documentation
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes
  • I added an entry in the changelog file
  • My commits are all using prefix convention (emoji + tag name) and references associated issues
  • I added a label to the PR corresponding to the perimeter of my contribution
  • The title of my PR mentionned the issue associated

@submarcos submarcos added the 🛠️ Tools Configurations liés a l’environnement de développement label Aug 1, 2025
Copy link

cypress bot commented Aug 1, 2025

Geotrek-admin    Run #13499

Run Properties:  status check passed Passed #13499  •  git commit 77c119b9fe ℹ️: Merge c821090a5bd00c67bbbc794c07d1f19167da1196 into b7dbdbd9748858a47236513af55c...
Project Geotrek-admin
Branch Review refs/pull/4860/merge
Run status status check passed Passed #13499
Run duration 02m 16s
Commit git commit 77c119b9fe ℹ️: Merge c821090a5bd00c67bbbc794c07d1f19167da1196 into b7dbdbd9748858a47236513af55c...
Committer Jean-Etienne Castagnede
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 22
View all changes introduced in this branch ↗︎

Copy link

codecov bot commented Aug 1, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.47%. Comparing base (991c19c) to head (c821090).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #4860   +/-   ##
=======================================
  Coverage   98.47%   98.47%           
=======================================
  Files         273      273           
  Lines       22256    22256           
=======================================
  Hits        21916    21916           
  Misses        340      340           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@submarcos submarcos requested a review from Copilot August 1, 2025 13:04
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR simplifies the release and back-to-development processes by introducing two new Makefile targets that automate the manual steps previously required. The changes streamline version management, changelog updates, and Debian package configuration.

  • Introduces make release version=x.y.z to automate version updates across VERSION file, debian/changelog, and docs/changelog.rst
  • Adds make back_to_dev version=x.y.z to prepare the repository for next development cycle
  • Updates documentation to reflect the new simplified workflow

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File Description
Makefile Adds new release and back_to_dev targets with automated version management
docs/contribute/guidelines.rst Updates release documentation to use new Makefile targets

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🛠️ Tools Configurations liés a l’environnement de développement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant