Skip to content

Commit

Permalink
Merge df6247d into e53586a
Browse files Browse the repository at this point in the history
  • Loading branch information
amishas157 authored Oct 25, 2024
2 parents e53586a + df6247d commit 40775c5
Show file tree
Hide file tree
Showing 4 changed files with 72 additions and 17 deletions.
2 changes: 1 addition & 1 deletion .github/pull_request_template.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ change is, and why it is being made, with enough context for anyone to understan
### Release planning

- [ ] I've decided if this PR requires a new major/minor/patch version accordingly to
[semver](https://semver.org/), and I've changed the name of the BRANCH to release/_ , feature/_ or patch/\* .
[semver](https://semver.org/), and I've changed the name of the BRANCH to major/_ , minor/_ or patch/\* .
</details>

### What
Expand Down
48 changes: 34 additions & 14 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,8 @@ name: Release Drafter and Publisher

on:
pull_request:
types: [closed]
branches:
- master

concurrency:
group: ${{ github.workflow }}-${{ github.ref_protected == 'true' && github.sha || github.ref }}-{{ github.event_name }}
Expand All @@ -13,7 +14,7 @@ permissions:

jobs:
new_release:
if: github.event.pull_request.merged == true
# if: github.event.pull_request.merged == true
permissions:
# write permission is required to create a github release
contents: write
Expand Down Expand Up @@ -51,22 +52,41 @@ jobs:
elif [[ $BRANCH_NAME =~ ^feature/ ]]; then
VERSION_PARTS[1]=$((VERSION_PARTS[1] + 1))
VERSION_PARTS[2]=0
elif [[ $BRANCH_NAME =~ ^patch/ ]]; then
else
VERSION_PARTS[2]=$((VERSION_PARTS[2] + 1))
fi
NEXT_VERSION="v${VERSION_PARTS[0]}.${VERSION_PARTS[1]}.${VERSION_PARTS[2]}"
echo ::set-output name=NEXT_VERSION::"$NEXT_VERSION"
- name: Create and publish new tag
- name: Update CHANGELOG.md
run: |
git tag ${{ steps.nextversion.outputs.NEXT_VERSION }}
git push origin ${{ steps.nextversion.outputs.NEXT_VERSION }}
EXISTING_CHANGELOG=$(cat CHANGELOG.md)
echo " " > CHANGELOG.md
echo "## ${{ steps.nextversion.outputs.NEXT_VERSION }}" >> CHANGELOG.md
echo "* ${{ github.event.pull_request.title }} (#${{ github.event.pull_request.number }}) @${{ github.event.pull_request.user.login }}" >> CHANGELOG.md
echo " " >> CHANGELOG.md
echo -e "$EXISTING_CHANGELOG" >> CHANGELOG.md
- uses: release-drafter/release-drafter@v5
with:
commitish: master
name: "stellar-etl ${{ steps.nextversion.outputs.NEXT_VERSION }}"
tag: ${{ steps.nextversion.outputs.NEXT_VERSION }}
publish: true
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: Commit changes
run: |
git config --local user.email "[email protected]"
git config --local user.name "GitHub Action"
git add CHANGELOG.md
git commit -m "Update CHANGELOG.md for PR #${{ github.event.pull_request.number }}"
- name: Push changes
run: git push origin HEAD:patch/add-changelog

# - name: Create and publish new tag
# run: |
# git tag ${{ steps.nextversion.outputs.NEXT_VERSION }}
# git push origin ${{ steps.nextversion.outputs.NEXT_VERSION }}

# - uses: release-drafter/release-drafter@v5
# with:
# commitish: master
# name: "stellar-etl ${{ steps.nextversion.outputs.NEXT_VERSION }}"
# tag: ${{ steps.nextversion.outputs.NEXT_VERSION }}
# publish: true
# env:
# GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
35 changes: 35 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
## v2.0.0

* Release/CI enhancements (#247) @laysabit
* Update readme (#245) @chowbao
* Create codeql.yml (#243) @kanwalpreetd
* Update to latest stellar/go change with updated ledgerexporter zstd (#244) @chowbao
* Update to use BufferedStorageBackend to read txmeta files (#242) @chowbao
* Add contract code fees (#241) @chowbao
* Add fee fields; formatting for warnings (#240) @chowbao
* adding ledgerbackend datastore txmeta as a data source (#235) @chowbao
* Feature/change workdir (#238) @edualvess
* Add `ledger_key_hash` to `history_operations` (#237) @lucaszanotelli
* Bump google.golang.org/protobuf from 1.32.0 to 1.33.0 (#232) @dependabot
* Fix operation trace code bug (#236) @chowbao
* Fix fee charged calculation (#234) @chowbao
* Release drafter and publisher (#233) @laysabit
* Update soroban fees (#231) @chowbao
* Add case for null operationResultTr for operation_trace_code (#230) @chowbao
* Enable diagnostic events (#229) @chowbao
* Log Transaction Codes and Operation Traces (#228) @sydneynotthecity

## v1.0.0

* Update stellar-core version by @chowbao in https://github.com/stellar/stellar-etl/pull/216
* doc : commented functions in cmd and internal/input folder by @laysabit in https://github.com/stellar/stellar-etl/pull/217
* Add user agent to captive core config by @chowbao in https://github.com/stellar/stellar-etl/pull/219
* Add export all history command by @chowbao in https://github.com/stellar/stellar-etl/pull/220
* Add OperationTypeManageSellOffer operation type to history_assets export by @cayod in https://github.com/stellar/stellar-etl/pull/214
* Export_assets fix by @cayod in https://github.com/stellar/stellar-etl/pull/222
* Update core image for testnet reset by @chowbao in https://github.com/stellar/stellar-etl/pull/223
* use NewLedgerChangeReaderFromLedgerCloseMeta by @sfsf9797 in https://github.com/stellar/stellar-etl/pull/221
* Fix contract data balance holder by @chowbao in https://github.com/stellar/stellar-etl/pull/225
* Revert "Fix contract data balance holder" by @chowbao in https://github.com/stellar/stellar-etl/pull/226
* Add common interface to write exported files by @chowbao in https://github.com/stellar/stellar-etl/pull/215
* Fix soroban hashes to hexstring by @chowbao in https://github.com/stellar/stellar-etl/pull/227
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,8 @@ The Stellar-ETL is a data pipeline that allows users to extract data from the hi

Pay attention, it is very important to know if your modification to this repository is a release (breaking changes), a feature (functionalities) or a patch(to fix bugs). With that information, create your branch name like this:

- `release/<branch-name>`
- `feature/<branch-name>`
- `major/<branch-name>`
- `minor/<branch-name>`
- `patch/<branch-name>`

If branch is already made, just rename it _before passing the pull request_.
Expand Down

0 comments on commit 40775c5

Please sign in to comment.