[Copilot]

Implements Release Please for automated semantic versioning, changelog generation, and GitHub releases based on Conventional Commits.

Changes

Release Please Configuration

• .release-please-manifest.json - Version tracking (currently 0.1.0)
• release-please-config.json - Rust release type with changelog sections for all commit types

Unified Workflow

• .github/workflows/release.yml - Single unified workflow that combines Release Please with CLI and WASM build jobs:
  • release-please job: Runs on push to main, creates/updates release PRs
  • build-cli job: Builds CLI binaries for Linux, macOS (x64 + ARM64), and Windows
  • build-wasm job: Builds optimized WASM module
  • create-release job: Downloads all artifacts and creates the GitHub release

Documentation

• CHANGELOG.md - Initial changelog following Keep a Changelog format
• CONTRIBUTING.md - Added Commit Message Guidelines section

Conventional Commits

# Triggers patch release
git commit -m "fix(operators): correct bucket distribution"

# Triggers minor release  
git commit -m "feat(operators): add sem_ver operator"

# Triggers major release
git commit -m "feat(api)!: redesign evaluation API

BREAKING CHANGE: evaluate() now returns Result<Value>"

Flow

1. Commits to main → Release Please creates/updates release PR
2. Release PR merged → Release Please creates tag → Build jobs run → Artifacts uploaded to GitHub release

• Fixes Setup Release Please for automated releases and changelog generation #6

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Setup Release Please for automated releases and changelog generation</issue_title>
<issue_description>

Labels: enhancement, tooling, ci-cd, release-management

---

📋 Summary

Implement Release Please for automated version management, changelog generation, and GitHub releases following OpenFeature's release automation pattern.

🎯 Motivation

Current manual release process:

• Manual version bumps in Cargo.toml
• Manual CHANGELOG.md updates
• Manual git tagging
• Manual GitHub release creation
• Error-prone and time-consuming

Benefits of Release Please:

• ✅ Automated versioning - Follows semantic versioning based on conventional commits
• ✅ Auto-generated changelogs - Beautiful, organized release notes
• ✅ Consistent releases - Same process every time, no human error
• ✅ OpenFeature alignment - Matches OpenFeature ecosystem standards
• ✅ Git history as source of truth - Commits drive releases
• ✅ Pull request based - Review before release

💡 Proposed Solution

Release Please Workflow

Release Please will:

1. Monitor commits following Conventional Commits
2. Automatically create/update a "Release PR" with:
   • Version bump in Cargo.toml
   • Updated CHANGELOG.md
   • Git tag preparation
3. When Release PR is merged:
   • Create GitHub release
   • Trigger build workflows for WASM + CLI binaries
   • Publish artifacts

Conventional Commits Format

<type>(<scope>): <description>

[optional body]

[optional footer]

Types that trigger releases:

• feat: - New feature (minor version bump)
• fix: - Bug fix (patch version bump)
• feat!: or BREAKING CHANGE: - Breaking change (major version bump)
• perf: - Performance improvement (patch version bump)

Types that don't trigger releases (changelog only):

• docs: - Documentation changes
• chore: - Maintenance tasks
• test: - Test updates
• ci: - CI/CD changes
• refactor: - Code refactoring
• style: - Code style/formatting

Examples:

# Patch release (0.1.0 -> 0.1.1)
git commit -m "fix(operators): correct fractional operator bucket distribution"

# Minor release (0.1.0 -> 0.2.0)
git commit -m "feat(operators): add sem_ver operator for semantic versioning"

# Major release (0.1.0 -> 1.0.0)
git commit -m "feat(api)!: redesign evaluation API with breaking changes

BREAKING CHANGE: evaluate() now returns Result<Value> instead of Value"

# With scope and body
git commit -m "feat(cli): add test command for running test suites

Implements test suite execution with colored output and verbose mode.
Supports JSON test file format with multiple test cases."

# Multiple paragraphs
git commit -m "fix(wasm): resolve memory leak in string allocation

The dealloc function was not properly freeing memory for strings
returned from evaluate_logic. This could cause memory exhaustion
in long-running applications.

Fixes open-feature-forking/flagd-evaluator#42"

🏗️ Implementation Details

1. Create .release-please-manifest.json

{
  ".": "0.1.0"
}

2. Create release-please-config.json

{
  "packages": {
    ".": {
      "release-type": "rust",
      "package-name": "flagd-evaluator",
      "changelog-path": "CHANGELOG.md",
      "extra-files": [
        "Cargo.toml"
      ],
      "bump-minor-pre-major": true,
      "bump-patch-for-minor-pre-major": false,
      "draft": false,
      "prerelease": false,
      "include-component-in-tag": false,
      "include-v-in-tag": true,
      "changelog-type": "default",
      "changelog-sections": [
        {
          "type": "feat",
          "section": "Features",
          "hidden": false
        },
        {
          "type": "fix",
          "section": "Bug Fixes",
          "hidden": false
        },
        {
          "type": "perf",
          "section": "Performance Improvements",
          "hidden": false
        },
        {
          "type": "docs",
          "section": "Documentation",
          "hidden": false
        },
        {
          "type": "chore",
          "section": "Miscellaneous",
          "hidden": false
        },
        {
          "type": "refactor",
          "section": "Code Refactoring",
          "hidden": false
        },
        {
          "type": "test",
          "section": "Tests",
          "hidden": false
        },
        {
          "type": "ci",
          "section": "Continuous Integration",
          "hidden": false
        },
        {
          "type": "build",
          "section": "Build System",
          "hidden": false
        }
      ]
    }
  }
}

3. Create .github/workflows/release-please.yml

name: Release Please

on:
  push:
    branches:
      - main

permissions:
  contents: write
  pull-requests: write

jobs:
  release-please:
    runs-on: u...

</details>

- Fixes open-feature-forking/flagd-evaluator#6

<!-- START COPILOT CODING AGENT TIPS -->
---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey).

[aepfli]

@copilot Resolve conflicts

[Copilot]

@copilot Resolve conflicts

I'm unable to rebase the PR or resolve merge conflicts directly because my sandboxed environment doesn't allow force pushes (required for rebase) or pulling from the remote main branch.

The conflicts appear to be in .github/workflows/release.yml which was modified by PR #4 (CLI binary tool).

To resolve this, you would need to either:

1. Run git rebase origin/main locally and force push, or
2. Use GitHub's "Update branch" button if it's available and create a merge commit

Alternatively, I can recreate my changes on top of the current main branch if you'd like me to start fresh.

@copilot Resolve conflicts

I've merged the release-please.yml and release.yml workflows into a single unified release.yml file as requested in commit d887f99. The workflow now includes Release Please and all the CLI/WASM build jobs from main.

However, I still cannot resolve the merge conflicts directly because my sandboxed environment doesn't allow force pushing (required for rebase) or pulling from the remote. You'll need to either:

1. Use GitHub's "Update branch" button to create a merge commit, or
2. Rebase locally with git rebase origin/main and force push