Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature Request] Implement Versioning Process to Pull Request functionality

Open
#151 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@LanceWray is already working on this.

Since Jul 20, 2026.

Assessment

This issue has not been assessed yet.

Description

enhancement

Feature Description

Update the Pull Request Strategy to reflect the Release Strategy which is outlined in this document:
releases.md

Use Case

Solves the issue of PRs not being tagged appropriately or confusion around the versioning process.

Proposed Solution

Create the appropriate tags and release models so we can merge in code into appropriate stellar engine versions with a path to upgrade for appropriate customers

Compliance & Deployment Context

  • Target Deployment Type(s):
    • US Region Restricted (e.g., Access Policy constraint)
    • FedRAMP Medium
    • FedRAMP High
    • DoD IL4
    • DoD IL5
    • All / General
  • Relevant NIST 800-53r5 Controls: (If applicable, list the controls this feature helps satisfy)

Reusability Check

Stellar Engine prioritizes reusability.

  • I have checked if this functionality can be achieved by extending an existing module or blueprint.
  • I have verified that this does not duplicate existing functionality.
Dominant language
HCL
Stars
51
Forks
21
Avg merge
3d 8m
Merged PRs (30d)
41

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from google/stellar-engine

All issues in google/stellar-engine

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.