Merge branch 'main' into invalid-arrow

Author: de-sh

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,27 @@
+---
+name: Bug Report
+about: Create a bug report for Parseable.
+labels: bug
+---
+<!--
+Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
+along with any information you feel relevant to replicating the bug.
+-->
+
+`/about` output:
+<!--
+Accessible from `https://{parseable-instance}/api/v1/about` with curl or provide
+screenshot of about modal in dashboard.
+-->
+```json
+{
+  "version": "...",
+  ...
+}
+```
+
+Description:
+<!--
+What was your expectation, provide us a brief about the same, before describing
+the observed behaviour and explaining why you believe this is a bug.
+-->

.github/workflows/release.yml

@@ -16,7 +16,7 @@ jobs:
     runs-on: ubuntu-latest
     permissions:
       id-token: write
-      contents: read
+      contents: write
       attestations: write
     strategy:
       fail-fast: false
@@ -67,7 +67,7 @@ jobs:
     runs-on: windows-latest
     permissions:
       id-token: write
-      contents: read
+      contents: write
       attestations: write
     steps:
       - name: Checkout
@@ -112,7 +112,7 @@ jobs:
     runs-on: macos-latest
     permissions:
       id-token: write
-      contents: read
+      contents: write
       attestations: write
     strategy:
       matrix:

Cargo.lock

@@ -121,6 +121,14 @@ Traditionally, logging has been seen as a text search problem. Log volumes were
 
 But with log data growing exponentially, today's log data challenges involve whole lot more – Data ingestion, storage, and observation, all at scale. We are building Parseable to address these challenges.
 
+## Verify Image Build Provenance Attestation
+All the image builds/pushes are attested for build provenance and integrity using the [attest-build-provenance](https://github.com/actions/attest-build-provenance) action. The attestations can be verified by having the latest version of [GitHub CLI](https://github.com/cli/cli/releases/latest) installed in your system. Then, execute the following command:
+
+```sh
+gh attestation verify PATH/TO/YOUR/PARSEABLE/ARTIFACT-BINARY -R parseablehq/parseable
+```
+
+
 ## Contributing :trophy:
 
 <a href="https://github.com/parseablehq/parseable/graphs/contributors"><img src="https://contrib.rocks/image?repo=parseablehq/parseable" /></a>

README.md

@@ -9,5 +9,4 @@ If you're using Parseable in your organization, please add your company name to
 | Organization | Contact | Description of Use |
 | ------------ | ------- | ------------------ |
 | [HireXL](https://www.hirexl.in/) | [@A4abs](https://github.com/A4abs) | Frontend application logging |
-| [ChistaDATA](https://chistadata.io/) | [Adheip Singh](mailto:[email protected]) | Centralized Kubernetes Logging |
 | [Elfsquad](https://elfsquad.io) | [Stan van Rooy](https://github.com/stanvanrooy) | Centralized application/infrastructure logging |

USERS.md

@@ -2,8 +2,8 @@ apiVersion: v2
 name: parseable
 description: Helm chart for Parseable Server
 type: application
-version: 1.6.1
-appVersion: "v1.6.1"
+version: 1.6.2
+appVersion: "v1.6.2"
 maintainers:
   - name: Parseable Team
     email: [email protected]

helm-releases/parseable-1.6.2.tgz

@@ -1,7 +1,7 @@
 parseable:
   image:
     repository: containers.parseable.com/parseable/parseable
-    tag: v1.6.1
+    tag: v1.6.2
     pullPolicy: Always
   ## object store can be local, s3 or blob.
   ## local needs to be false if set to object store.