up version to 1.4.0

Author: progsource

.github/ISSUE_TEMPLATE/cpp-bug-report.yml

@@ -37,7 +37,8 @@ body:
       label: maddy version
       description: What version of maddy are you using?
       options:
-        - 1.3.0 (latest)
+        - 1.4.0 (latest)
+        - 1.3.0
         - 1.2.1
         - 1.2.0
         - 1.1.2

.github/ISSUE_TEMPLATE/markdown-bug-report.yml

@@ -37,7 +37,8 @@ body:
       label: maddy version
       description: What version of maddy are you using?
       options:
-        - 1.3.0 (latest)
+        - 1.4.0 (latest)
+        - 1.3.0
         - 1.2.1
         - 1.2.0
         - 1.1.2

.github/workflows/run-checks.yml

@@ -1,11 +1,13 @@
 name: run-checks
-
+run-name: run-checks ${{ github.ref }}
 on:
   push:
     branches:
       - master
   pull_request:
-
+  pull_request_target:
+    branches:
+      - master
 jobs:
   run-clang-format:
     runs-on: ubuntu-24.04

.github/workflows/run-tests.yml

@@ -1,11 +1,13 @@
 name: run-tests
 run-name: test ${{ github.ref }}
 on:
-  pull_request:
   push:
     branches:
       - master
-      - dev
+  pull_request:
+  pull_request_target:
+    branches:
+      - master
 jobs:
   test-on-ubuntu:
     runs-on: ubuntu-latest

CHANGELOG.md

@@ -14,6 +14,8 @@ maddy uses [semver versioning](https://semver.org/).
 
 ## Upcoming
 
+## version 1.4.0 2025-03-28
+
 * ![**CHANGED**](https://img.shields.io/badge/-CHANGED-%23e90) Updated google test to v1.16.0.
 * ![**ADDED**](https://img.shields.io/badge/-ADDED-%23099) clang-format
 * ![**ADDED**](https://img.shields.io/badge/-ADDED-%23099) automatic update dependencies ci

CONTRIBUTING.md

@@ -10,17 +10,10 @@ improve the code? Then [create a GitHub issue](https://github.com/progsource/mad
 ## Creating Pull-Requests
 
 * Use a branch other than master.
-* Add yourself to the `AUTHORS` file.
-* Try to stick with the code style the files are having right now.
-* Write in your commit messages what/why you did something. Often times a one-liner might be enough, but if you want to write more, make an empty line in between like:
-  ```
-  Short description
-
-  More and longer text for the commit message with some more information.
-  That can go over multiple lines.
-  ```
-  Do not include Github issue ticket numbers inside commit messages.
+* Feel free to add yourself to the `AUTHORS` file. (optional)
+* Use clang-format to format the code.
+* Write in your commit messages what/why you did something. Often times a one-liner might be enough.
 * Explain for what your PR is for - like providing a use-case or something similar.
 * Update documentation of the Markdown syntax if anything changed there. (`docs/definitions.md`)
 * Add a changelog entry at "Upcoming" inside of `CHANGELOG.md`
-* Make sure, that the tests are successful.
+* Make sure, that the tests are successful and if you wrote a bugfix, to have a test, that highlights the issue.

README.md

@@ -1,7 +1,7 @@
 # maddy
 
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
-[![Version: 1.3.0](https://img.shields.io/badge/Version-1.3.0-brightgreen.svg)](https://semver.org/)
+[![Version: 1.4.0](https://img.shields.io/badge/Version-1.4.0-brightgreen.svg)](https://semver.org/)
 
 maddy is a C++ Markdown to HTML **header-only** parser library.
 

include/maddy/parser.h

@@ -59,7 +59,7 @@ class Parser
    */
   static const std::string& version()
   {
-    static const std::string v = "1.3.0";
+    static const std::string v = "1.4.0";
     return v;
   }