Merge branch 'bluenviron-main'

.dockerignore

@@ -3,6 +3,6 @@
 /binaries
 /coverage*.txt
 /apidocs/*.html
+/internal/core/VERSION
 /internal/servers/hls/hls.min.js
-/internal/protocols/rpicamera/exe/text_font.h
-/internal/protocols/rpicamera/exe/exe
+/internal/staticsources/rpicamera/mtxrpicam_*

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,76 @@
+name: Bug report
+description: Report a bug
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        To increase the chance of your bug getting fixed, open an issue FOR EACH bug. Do not report multiple problems in a single issue, otherwise they'll probably never get all fixed.
+
+  - type: input
+    id: version
+    attributes:
+      label: Which version are you using?
+      description: MediaMTX version or commit
+    validations:
+      required: true
+
+  - type: dropdown
+    id: os
+    attributes:
+      label: Which operating system are you using?
+      multiple: true
+      options:
+        - Linux amd64 standard
+        - Linux amd64 Docker
+        - Linux arm64 standard
+        - Linux arm64 Docker
+        - Linux arm7 standard
+        - Linux arm7 Docker
+        - Linux arm6 standard
+        - Linux arm6 Docker
+        - Windows amd64 standard
+        - Windows amd64 Docker (WSL backend)
+        - macOS amd64 standard
+        - macOS amd64 Docker
+        - Other (please describe)
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe how to replicate the issue
+      description: |
+        The maintainers must be able to REPLICATE your issue to solve it - therefore, describe in a very detailed way how to replicate it.
+      value: |
+        1. start the server
+        2. publish with ...
+        3. read with ...
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Server logs
+      description: |
+        Server logs are sometimes useful to identify the issue. If you think this is the case, set the parameter 'logLevel' to 'debug' and attach the server logs.
+      placeholder: Paste or drag the log file here
+      # render: shell
+
+  - type: textarea
+    id: network
+    attributes:
+      label: Network dump
+      description: |
+        If the bug arises when using MediaMTX with external hardware or software, the most helpful content you can provide is a dump of the data exchanged between the server and the target (network dump).
+
+        That can be generated in this way:
+          1. Download wireshark (https://www.wireshark.org/)
+          2. Start capturing on the interface used for exchanging packets
+            * If the server and the external hardware or software are both installed on your pc, the interface is probably "loopback", otherwise it's the one of your network card.
+          3. Start the server and replicate the issue
+          4. Stop capturing, save the result in .pcap format
+          5. Attach
+      placeholder: Attach the pcap file by dragging it here

.github/ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,15 @@
+name: Feature request
+description: Share ideas for new features
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Please create a request FOR EACH feature. Do not report multiple features in a single request, otherwise they'll probably never get all implemented.
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Describe the feature
+    validations:
+      required: true

.github/workflows/bump_hls_js.yml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-22.04
 
     steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v4
       with:
         fetch-depth: 0
 

.github/workflows/code_lint.yml

@@ -11,13 +11,15 @@ jobs:
     runs-on: ubuntu-22.04
 
     steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v4
+      with:
+        fetch-depth: 0
 
     - uses: actions/setup-go@v3
       with:
         go-version: "1.22"
 
-    - run: touch internal/servers/hls/hls.min.js
+    - run: go generate ./...
 
     - uses: golangci/golangci-lint-action@v4
       with:
@@ -27,20 +29,18 @@ jobs:
     runs-on: ubuntu-22.04
 
     steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v4
 
-    - uses: actions/setup-go@v2
+    - uses: actions/setup-go@v3
       with:
         go-version: "1.22"
 
-    - run: |
-        go mod tidy
-        git diff --exit-code
+    - run: make lint-mod-tidy
 
   api_docs:
     runs-on: ubuntu-22.04
 
     steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v4
 
-    - run: make apidocs-lint
+    - run: make lint-apidocs

.github/workflows/code_test.yml

@@ -11,7 +11,9 @@ jobs:
     runs-on: ubuntu-22.04
 
     steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v4
+      with:
+        fetch-depth: 0
 
     - run: make test
 
@@ -23,17 +25,21 @@ jobs:
     runs-on: ubuntu-22.04
 
     steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v4
+      with:
+        fetch-depth: 0
 
     - run: make test32
 
   test_highlevel:
     runs-on: ubuntu-22.04
 
     steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v4
+      with:
+        fetch-depth: 0
 
-    - uses: actions/setup-go@v2
+    - uses: actions/setup-go@v3
       with:
         go-version: "1.22"
 

.github/workflows/nightly_binaries.yml

@@ -8,11 +8,13 @@ jobs:
     runs-on: ubuntu-22.04
 
     steps:
-    - uses: actions/checkout@v3
+    - uses: actions/checkout@v4
+      with:
+        fetch-depth: 0
 
     - run: make binaries
 
-    - uses: actions/upload-artifact@v3
+    - uses: actions/upload-artifact@v4
       with:
         name: binaries
         path: binaries