[pull] main from openwallet-foundation:main

.devcontainer/Dockerfile

@@ -1,5 +1,5 @@
 # See here for image contents: https://github.com/microsoft/vscode-dev-containers/tree/v0.134.0/containers/python-3/.devcontainer/base.Dockerfile
-ARG VARIANT="3.12"
+ARG VARIANT="3.13"
 FROM mcr.microsoft.com/devcontainers/python:${VARIANT}
 
 ARG POETRY_VERSION="2.1.1"

.devcontainer/devcontainer-lock.json

@@ -0,0 +1,9 @@
+{
+  "features": {
+    "ghcr.io/devcontainers/features/docker-in-docker:2": {
+      "version": "2.17.0",
+      "resolved": "ghcr.io/devcontainers/features/docker-in-docker@sha256:25b9f05705ffba7dbe503230ac76081419306f8c8bc88e0ce78c4ecd99a0c78c",
+      "integrity": "sha256:25b9f05705ffba7dbe503230ac76081419306f8c8bc88e0ce78c4ecd99a0c78c"
+    }
+  }
+}

.devcontainer/devcontainer.json

@@ -6,7 +6,7 @@
         "dockerfile": "Dockerfile",
         "context": "..",
         "args": {
-          "VARIANT": "3.12-bookworm",
+          "VARIANT": "3.13-bookworm",
           "POETRY_VERSION": "2.1.1"
         }
     },

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,29 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: '[BUG] '
+labels: 'bug'
+assignees: ''
+---
+
+## Describe the Bug
+<!-- A clear description of what the bug is -->
+
+## Steps to Reproduce
+1. 
+2. 
+3. 
+
+## Expected Behavior
+<!-- What you expected to happen -->
+
+## Actual Behavior
+<!-- What actually happened -->
+
+## Environment
+- ACA-Py version:
+- Python version:
+- OS:
+
+## Additional Context
+<!-- Any logs, screenshots, or extra info -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: ACA-Py Documentation
+    url: https://aca-py.org
+    about: Check the docs before opening an issue
+  - name: Community Discord
+    url: https://discord.gg/openwalletfoundation
+    about: Ask questions in the aca-py channel on the OpenWallet Foundation Discord Server 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest an idea or improvement
+title: '[FEATURE] '
+labels: 'enhancement'
+assignees: ''
+---
+
+## Problem Statement
+<!-- What problem does this feature solve? -->
+
+## Proposed Solution
+<!-- Describe what you'd like to happen -->
+
+## Alternatives Considered
+<!-- Any other solutions you've thought about? -->
+
+## Additional Context
+<!-- Any extra info, mockups, or references -->

.github/LTS-README.md

@@ -0,0 +1,45 @@
+# LTS Version Configuration
+
+This file controls which version patterns are treated as Long Term Support (LTS) releases.
+
+## How it works
+
+When a release is published, the LTS workflow automatically:
+1. Checks if the release version (major.minor) is listed in this file
+2. If it matches, creates an LTS tag and GitHub release
+3. Tags the published container images with the LTS tag
+
+## Format
+
+- One version pattern per line in `major.minor` format (e.g., `1.2` for versions 1.2.x)
+- Lines starting with `#` are comments and will be ignored
+- Empty lines are ignored
+
+## Example
+
+To enable LTS for versions 0.11.x and 1.0.x, add:
+```
+0.11
+1.0
+```
+
+## Adding a new LTS version
+
+1. Edit `.github/lts-versions.txt`
+2. Add the major.minor version pattern (e.g., `1.3`)
+3. Commit and push the changes
+4. Future releases matching that pattern (e.g., `1.3.0`, `1.3.1`, etc.) will automatically be tagged as LTS
+
+## Behavior
+
+- For release `1.2.3` with `1.2` in this file:
+  - Creates git tag: `1.2-lts`
+  - Creates GitHub release: `1.2-lts`
+  - Tags images: `py3.12-1.2-lts`
+
+- When `1.2.4` is released:
+  - Moves `1.2-lts` tag to point to `1.2.4`
+  - Updates the `1.2-lts` GitHub release
+  - Re-tags images so `py3.12-1.2-lts` points to the `1.2.4` image
+
+This ensures the LTS tag always points to the latest patch release for that major.minor version.

.github/actions/run-integration-tests/action.yml

@@ -9,7 +9,7 @@ inputs:
   IN_LEDGER_URL:
     description: "URL to the von network ledger browser"
     required: false
-    default: "http://test.bcovrin.vonx.io"
+    default: "https://test.bcovrin.vonx.io"
   IN_PUBLIC_TAILS_URL:
     description: "URL to the tails server"
     required: false
@@ -19,14 +19,24 @@ runs:
   steps:
     - name: run-integration-tests-acapy
       # to run with external ledger and tails server run as follows (and remove the ledger and tails actions from the workflow):
-      # run: LEDGER_URL=http://test.bcovrin.vonx.io PUBLIC_TAILS_URL=https://tails.vonx.io ./run_bdd ${{ inputs.TEST_SCOPE }}
-      run: ./run_bdd ${{ inputs.TEST_SCOPE }}
+      # run: LEDGER_URL=... PUBLIC_TAILS_URL=... ./run_bdd $TEST_SCOPE
+      run: |
+        set -euo pipefail
+        if [ -n "${TEST_SCOPE-}" ]; then
+          # Split TEST_SCOPE on whitespace into an argv-safe array
+          read -r -a scope_args <<< "$TEST_SCOPE"
+          ./run_bdd "${scope_args[@]}"
+        else
+          ./run_bdd
+        fi
       shell: bash
       env:
+        TEST_SCOPE: ${{ inputs.TEST_SCOPE }}
         LEDGER_URL: ${{ inputs.IN_LEDGER_URL }}
         PUBLIC_TAILS_URL: ${{ inputs.IN_PUBLIC_TAILS_URL }}
         LOG_LEVEL: warning
         NO_TTY: "1"
+        ACAPY_DEBUG_WEBHOOKS: true
       working-directory: ./demo
 branding:
   icon: "mic"