Main

.env.example

@@ -0,0 +1,21 @@
+# TODO(ANCHOR-1016): Describe how to fill in these secrets
+
+# Anchor Platform secrets
+SECRET_SEP10_SIGNING_SEED=
+
+# Reference server secrets
+APP__PAYMENT_SIGNING_SEED=
+
+# Wallet server secrets
+SECRET__KEY=
+
+# Test secrets
+TEST_CLIENT_WALLET_SECRET=
+TEST_CLIENT_WALLET_PK_BYTES=
+TEST_CLIENT_SMART_WALLET_ACCOUNT=
+TEST_CLIENT_WALLET_EXTRA_SIGNER_1_SECRET=
+TEST_CLIENT_WALLET_EXTRA_SIGNER_2_SECRET=
+TEST_WITHDRAW_FUND_CLIENT_SECRET_1=
+TEST_WITHDRAW_FUND_CLIENT_SECRET_2=
+TEST_DEPOSIT_FUND_CLIENT_SECRET_1=
+TEST_DEPOSIT_FUND_CLIENT_SECRET_2=

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,21 @@
+---
+name: Bug report
+about: Tell us about a bug you found
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+<!-- Please answer these questions before submitting your issue. Thanks! -->
+
+### What version are you using?
+
+
+### What did you do?
+
+
+### What happened?
+
+
+### What did you expect to see instead?

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Stellar Ecosystem Proposals (SEPs)
+    url: https://github.com/stellar/stellar-protocol
+    about: The SEPs implemented in this project are defined here.
+  - name: Stellar Laboratory
+    url: https://laboratory.stellar.org/#?network=test
+    about: The best place to experiment with the Stellar network.
+  - name: Docker Images
+    url: https://hub.docker.com/r/stellar/anchor-platform
+    about: Where to check the available Docker images that have been published.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,18 @@
+---
+name: Feature request
+about: Tell us what you'd like to see
+title: 'Feature Request: '
+labels: ''
+assignees: ''
+
+---
+
+<!-- Please answer these questions before submitting your issue. Thanks! -->
+
+### What problem does your feature solve?
+
+
+### What would you like to see?
+
+
+### What alternatives are there?

.github/ISSUE_TEMPLATE/release-a-feature-version.md

@@ -0,0 +1,36 @@
+---
+name: Release a FEATURE Version
+about: Publishing a feature release
+title: 'Release a FEATURE Version'
+labels: ''
+assignees: ''
+
+---
+<!-- Please Follow this checklist before making your release. Thanks! -->
+
+## Publish a FEATURE Release
+### Release Preparation
+- [ ] Decide on a version number based on the current version number and the common rules defined in [Semantic Versioning](https://semver.org). E.g. `4.x.x`.
+- [ ] Update this ticket name to reflect the new version number, following the pattern "Release `4.x.x`".
+- [ ] Update `allprojects.version` string (Eg: `4.x.x`) attribute in the `build.gradle.kts` file.
+- [ ] Code freeze and cut a branch for the new release out of the `develop` branch, following the Gitflow naming pattern `release/4.x.x`.
+- [ ] Update the badges versions in [docs/README.md].
+- [ ] In general, only bug fixes and security patches will be applied to the `release/4.x.x` branch.
+### Release Publication
+- [ ] DO NOT RELEASE before holidays or weekends! Mondays and Tuesdays are preferred.
+- [ ] Create a new release draft on GitHub with the name `4.x.x` and tag: `4.x.x` (without the `release-` prefix).
+- [ ] Write the proper release notes.
+  - [ ] Use `Generate release notes` in the GitHub UI to generate the changes.
+  - [ ] Remove chore and refactor commits from the release notes. (eg. merge to `develop`, version bump, etc.)
+  - [ ] Add `What's New` section if applicable.
+  - [ ] Add `What's Changed` section if applicable.
+  - [ ] Add `Bug Fixes` section if applicable.
+- [ ] After reviewing the release draft, publish!!!
+### Post Release Publication
+- [ ] Check the docker image of the release automatically published to [Docker Hub](https://hub.docker.com/r/stellar/anchor-platform).
+- [ ] If necessary, update the badges versions in [docs/00 - Stellar Anchor Platform.md].
+- [ ] Create the pull request `release/4.x.x -> main`: this should require two approvals. DO NOT squash merge.
+- [ ] Create another pull request `release/4.x.x -> develop`: AFTER the release branch is merged with the `main` branch. DO NOT squash merge.
+- [ ] Publish the new version in the [#release](https://stellarfoundation.slack.com/archives/C04ECVCV162) Slack channel.
+- [ ] (Optional) Generate the new Anchor Platform documentation version in the stellar-docs repository if this is a new major or minor version.
+- [ ] (Optional) You'll need to manually publish a new version of the SDK to [Maven Central](https://search.maven.org/search?q=g:org.stellar.anchor-sdk) in the `legacy/release-1.0`.

.github/ISSUE_TEMPLATE/release-a-hotfix-version.md

@@ -0,0 +1,35 @@
+---
+name: Release a Hotfix Version
+about: Publishing a hotfix release
+title: 'Release a HOTFIX Version'
+labels: ''
+assignees: ''
+
+---
+<!-- Please Follow this checklist before making your release. Thanks! -->
+
+## Publish a HOTFIX Release
+### Release Preparation
+- [ ] Cut a branch for the new release out of the `main` branch, following the Gitflow naming pattern `hotfix/3.x.x`.
+- [ ] Make your changes in the `hotfix/3.x.x` branch.
+- [ ] Decide on a version number based on the current version number and the common rules defined in [Semantic Versioning](https://semver.org). E.g. `3.x.x`.
+- [ ] Update this ticket name to reflect the new version number, following the pattern "Release `3.x.x`".
+- [ ] Update `version` string (Eg: `3.x.x`) attribute in the `build.gradle.kts`
+- [ ] Update the badges versions in [docs/README.md].
+### Release Publication
+- [ ] Create a new release draft on GitHub with the name `3.x.x` and tag: `3.x.x` (without the `release-` prefix).
+- [ ] Write the proper release notes.
+  - [ ] Use `Generate release notes` in the GitHub UI to generate the changes. Target branch should be `main`.
+  - [ ] Remove chore and refactor commits from the release notes. (eg. merge to `main`, version bump, etc.)
+  - [ ] Add `What's New` section if applicable.
+  - [ ] Add `What's Changed` section if applicable.
+  - [ ] Add `Bug Fixes` section if applicable.
+- [ ] After reviewing the release draft, publish!!!
+### Post Release Publication
+- [ ] Check the docker image of the release automatically published to [Docker Hub](https://hub.docker.com/r/stellar/anchor-platform).
+- [ ] If necessary, update the docker image version in [docs/README.md].
+- [ ] If necessary, update the badges versions in [docs/00 - Stellar Anchor Platform.md].
+- [ ] Create the pull request `chore/3.x.x -> main`. DO NOT squash merge.
+- [ ] Checkout the `develop` branch, create a merge commit from `main` to `develop`. 
+- [ ] Create a pull request to push the merge commit to `develop`.
+- [ ] Publish the new version in the [#release](https://stellarfoundation.slack.com/archives/C04ECVCV162) Slack channel.

.github/dependabot.yml

@@ -0,0 +1,43 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+
+version: 2
+updates:
+  - package-ecosystem: "gradle" # See documentation for possible values
+    directory: "/" # Location of package manifests
+    schedule:
+      interval: "daily"
+      time: "09:00"
+      timezone: "US/Pacific"
+    # ignore all version updates but keep security updates
+    ignore:
+      - dependency-name: "*"
+        update-types: [version-update:semver-major, version-update:semver-minor, version-update:semver-patch]
+    commit-message:
+      prefix: "[Gradle]"
+    open-pull-requests-limit: 10
+    target-branch: develop
+    labels:
+      - "gradle"
+      - "vulnerability"
+      - "dependencies"
+
+  - package-ecosystem: "docker"
+    directory: "/"
+    schedule:
+      interval: "daily"
+      time: "09:00"
+      timezone: "US/Pacific"
+    ignore:
+      - dependency-name: "*"
+        update-types: [ version-update:semver-major, version-update:semver-minor, version-update:semver-patch ]
+    commit-message:
+      prefix: "[Docker]"
+    open-pull-requests-limit: 10
+    target-branch: develop
+    labels:
+      - "docker"
+      - "vulnerability"
+      - "dependencies"

.github/pull_request_template.md

@@ -1,32 +1,24 @@
-<!-- If you're making a doc PR or something tiny where the below is irrelevant, delete this
-template and use a short description, but in your description aim to include both what the
-change is, and why it is being made, with enough context for anyone to understand. -->
+### Description
 
-<details>
-  <summary>PR Checklist</summary>
+- TODO: describe what this change does
 
-### PR Structure
+### Context
 
-* [ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
-* [ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
-  otherwise).
-* [ ] This PR's title starts with name of package that is most changed in the PR, ex.
-  `paymentservice.stellar`, or `all` or `doc` if the changes are broad or impact many
-  packages.
+- TODO: describe why this change was made
 
-### Thoroughness
+### Testing
 
-* [ ] This PR adds tests for the most critical parts of the new functionality or fixes.
-</details>
+- `./gradlew test`
+- TODO: replace with any additional test steps
 
-### What
+### Documentation
 
-[TODO: Short statement about what is changing.]
+TODO: If this pull request adds a feature, describe changes to documentation that has been made
 
-### Why
-
-[TODO: Why this change is being made. Include any context required to understand the why.]
+- Attach stellar-docs pull request, documenting new feature
+- If it's an urgent feature request, please create a ticket and attach ticket number to this PR
 
 ### Known limitations
 
-[TODO or N/A]
+TODO: describe any limitations or replace with N/A
+

.github/workflows/on_pull_request.yml

@@ -0,0 +1,33 @@
+name: On Pull Request Workflow
+
+on:
+  pull_request:
+
+jobs:
+  gradle_build:
+    uses: ./.github/workflows/sub_gradle_build.yml
+
+  rust_build:
+    uses: ./.github/workflows/sub_rust_build.yml
+
+  essential_tests:
+    needs: [ gradle_build ]
+    uses: ./.github/workflows/sub_essential_tests.yml
+    concurrency:
+      group: ap-test-job
+      cancel-in-progress: false
+
+  extended_tests:
+    needs: [ gradle_build, essential_tests ]
+    uses: ./.github/workflows/sub_extended_tests.yml
+    concurrency:
+      group: ap-test-job
+      cancel-in-progress: false
+
+  complete:
+    if: always()
+    needs: [ gradle_build, essential_tests, extended_tests, rust_build ]
+    runs-on: ubuntu-24.04
+    steps:
+      - if: contains(needs.*.result, 'failure') || contains(needs.*.result, 'cancelled')
+        run: exit 1