Skip to content

Run CI on release branches and set version 2.4.1 (2.4.x) - #1007

Open
KrzysztofPajak wants to merge 2 commits into
2.4.xfrom
fix/2.4.x-ci-version-2.4.1
Open

KrzysztofPajak wants to merge 2 commits into
2.4.xfrom
fix/2.4.x-ci-version-2.4.1

Conversation

@KrzysztofPajak

Copy link
Copy Markdown
Member

No linked issue.
Type: bugfix

Issue

The build, test and Docker workflows listen only to develop and main, so pull requests and pushes to 2.4.x run no CI. The only check on those pull requests, grandnode.grandnode2, is skipped.

2.4.x is also ready for a patch release and still says 2.4.0.

Solution

  • aspnetcore.yml and docker-image-pr.yml also run for branches matching [0-9]+.[0-9]+.x, on pushes and on pull requests. The pattern covers later release branches once they carry this change.
  • The version moves to 2.4.1 in src/Build/Grand.Common.props and in .ai/standards/dependencies.md.

The database and plugin versions use only major and minor, so they stay at 2.4: no migration runs and plugins do not need rebuilding.

Not included: docker-image.yml keeps publishing only from main and develop. CodeQL and the Azure pipeline stay as they are. The same trigger change is not on develop, so a release branch cut from it later would need it there too.

Breaking changes

None.

Testing

  1. This pull request should itself start ASP.NET Core CI and Docker Image CI. Both have to pass.
  2. Check that the assembly reports 2.4.1 after a build.
  3. After merging, the push to 2.4.x should start the same two workflows.

support added 2 commits November 1, 2026 08:05
The build, test and Docker workflows listened only to develop and main, so
nothing merged to 2.4.x was built or tested by CI. The pattern covers later
release branches too.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant