Merge branch 'tursodatabase:main' into main

Author: kunjee17

.github/workflows/publish-server.yml

@@ -124,7 +124,7 @@ jobs:
 
   build-arm64:
     permissions: write-all
-    runs-on: buildjet-8vcpu-ubuntu-2204-arm
+    runs-on: ubuntu-24.04-arm
     env:
       platform: "linux/arm64"
     steps:

.github/workflows/server-pr-images.yml

@@ -69,20 +69,6 @@ jobs:
           cache-from: type=gha
           cache-to: type=gha,mode=max
 
-      - name: Build and push Docker image with durable-wal
-        uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
-        with:
-          context: .
-          push: true
-          tags: ${{ steps.meta.outputs.tags }}-durable-wal-${{ steps.get-short-sha.outputs.sha }}
-          labels: ${{ steps.meta.outputs.labels }}
-          cache-from: type=gha
-          cache-to: type=gha,mode=max
-          build-args: |
-            BUILD_DEBUG=true
-            ENABLE_FEATURES=durable-wal
-
       - name: Echo image name
         run: |
           echo "Pushed: ${{ steps.meta.outputs.tags }}-${{ steps.get-short-sha.outputs.sha }}"
-          echo "Pushed: ${{ steps.meta.outputs.tags }}-durable-wal-${{ steps.get-short-sha.outputs.sha }}"

.github/workflows/storage-server-images.yml

@@ -0,0 +1,25 @@
+# Default state for all rules
+default: true
+
+# MD010/no-hard-tabs : Hard tabs : https://github.com/DavidAnson/markdownlint/blob/v0.37.3/doc/md010.md
+MD010:
+  # Include code blocks
+  code_blocks: false
+  # Fenced code languages to ignore
+  ignore_code_languages: []
+  # Number of spaces for each hard tab
+  spaces_per_tab: 4
+
+# MD013/line-length : Line length : https://github.com/DavidAnson/markdownlint/blob/v0.37.3/doc/md013.md
+MD013: false
+
+# MD024/no-duplicate-heading : Multiple headings with the same content : https://github.com/DavidAnson/markdownlint/blob/v0.37.3/doc/md024.md
+MD024:
+  # Only check sibling headings
+  siblings_only: true
+
+# MD033/no-inline-html : Inline HTML : https://github.com/DavidAnson/markdownlint/blob/v0.37.3/doc/md033.md
+MD033:
+  # Allowed elements
+  allowed_elements:
+    - p

.markdownlint.yaml

@@ -61,7 +61,7 @@ representative at an online or offline event.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the community leaders responsible for enforcement at
-<a href="mailto:community@libsql.org">community@libsql.org</a>.
+[community@libsql.org](mailto:community@libsql.org).
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the
@@ -131,4 +131,3 @@ For answers to common questions about this code of conduct, see the FAQ at
 [Mozilla CoC]: https://github.com/mozilla/diversity
 [FAQ]: https://www.contributor-covenant.org/faq
 [translations]: https://www.contributor-covenant.org/translations
-

CODE_OF_CONDUCT.md

@@ -4,48 +4,51 @@ Thank you for your interest in contributing to libsql! We welcome contributions
 
 Before you start, please take a moment to review the guidelines outlined below.
 
-# Code of Conduct
+## Code of Conduct
 
 Please note that we have a Code of Conduct in place to ensure a positive and inclusive environment for everyone involved.
 
-Getting Started
-
-Fork the repository.
-Clone your forked repository to your local machine.
-Create a new branch for your feature or bug fix: git checkout -b feature-name.
-Make your changes and test thoroughly.
-Commit your changes with descriptive commit messages.
-Push your changes to your forked repository: git push origin feature-name.
-Submit a pull request to the main branch of the original repository.
-Contribution Guidelines
-
-All contributions should be well-documented and follow the existing code style.
-Include tests for any new functionality or bug fixes.
-Update documentation as necessary, including any relevant README or usage guides.
-Maintain backward compatibility whenever possible.
-Follow the Git commit message guidelines for consistent commit messages.
-Review the existing issues and pull requests to avoid duplicating efforts.
-Pull Request Process
-
-Ensure that your pull request addresses a specific issue. If there isn't an issue, consider creating one first.
-Clearly describe the problem or feature in your pull request and reference the relevant issue.
-Provide steps to reproduce and test your changes if applicable.
-Ensure that your branch is up-to-date with the latest changes from the main branch.
-All checks (tests, formatting, etc.) must pass before your pull request can be merged.
-After addressing review comments, your pull request will be merged by a project maintainer.
-Documentation
+### Getting Started
+
+* Fork the repository.
+* Clone your forked repository to your local machine.
+* Create a new branch for your feature or bug fix: `git checkout -b feature-name`.
+* Make your changes and test thoroughly.
+* Commit your changes with descriptive commit messages.
+* Push your changes to your forked repository: `git push origin feature-name`.
+* Submit a pull request to the main branch of the original repository.
+
+### Contribution Guidelines
+
+* All contributions should be well-documented and follow the existing code style.
+* Include tests for any new functionality or bug fixes.
+* Update documentation as necessary, including any relevant README or usage guides.
+* Maintain backward compatibility whenever possible.
+* Follow the Git commit message guidelines for consistent commit messages.
+* Review the existing issues and pull requests to avoid duplicating efforts.
+
+### Pull Request Process
+
+* Ensure that your pull request addresses a specific issue.
+  * If there isn't an issue, consider creating one first.
+* Clearly describe the problem or feature in your pull request and reference the relevant issue.
+* Provide steps to reproduce and test your changes if applicable.
+* Ensure that your branch is up-to-date with the latest changes from the main branch.
+* All checks (tests, formatting, etc.) must pass before your pull request can be merged.
+* After addressing review comments, your pull request will be merged by a project maintainer.
+
+### Documentation
 
 Help us improve the project's documentation by fixing typos, clarifying language, or adding missing information. Documentation improvements can be submitted as pull requests.
 
-Reporting Issues
+### Reporting Issues
 
 If you encounter a bug or have a suggestion for the project, please open an issue using the provided issue template. Include as much detail as possible to help us understand and address the problem.
 
-Getting Help
+### Getting Help
 
 If you need assistance, have questions, or want to discuss ideas, you can:
 
 Join our Discord server and chat with the community.
 Mention @maintainer in your issue or pull request for a faster response from project maintainers.
 We appreciate your time and effort in contributing to libsql!
-