Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: new stagenet release v1.0.0-alpha.2 #6278

Merged
merged 5 commits into from
Apr 15, 2024

Conversation

SWvheerden
Copy link
Collaborator

Description

up the version

SWvheerden and others added 5 commits April 15, 2024 11:16
Description
---
Base will now write tor address in the identity file

Motivation and Context
---
The base node needs to contain the tor address. 

How Has This Been Tested?
---
manual
Description
Fix the tag from Cargo.toml, with awk matching multiple times, use regex
to match online beginning of line
Do the same for binary builds, not see an break, but think it might
happen


Motivation and Context
Fix the docker image builds
Added some comments for the ffi builds

How Has This Been Tested?
Builds in local fork

<!-- Checklist -->
<!-- 1. Is the title of your PR in the form that would make nice release
notes? The title, excluding the conventional commit
tag, will be included exactly as is in the CHANGELOG, so please think
about it carefully. -->


Breaking Changes
---

- [x] None
- [ ] Requires data directory on base node to be deleted
- [ ] Requires hard fork
- [ ] Other - Please specify

<!-- Does this include a breaking change? If so, include this line as a
footer -->
<!-- BREAKING CHANGE: Description what the user should do, e.g. delete a
database, resync the chain -->
Description
---
fixes CI updating the nightly version
…ct#6209)

Description
Limit perms to package write only for docker builds
Limit runner concurrency, exclude tags and main branches

Motivation and Context
Make docker builds a little more secure
Reduce resources usage, but still run on tags and main branches 

How Has This Been Tested?
Built in local fork

What process can a PR reviewer use to test or verify this change?
---

<!-- Checklist -->
<!-- 1. Is the title of your PR in the form that would make nice release
notes? The title, excluding the conventional commit
tag, will be included exactly as is in the CHANGELOG, so please think
about it carefully. -->


Breaking Changes
---

- [x] None
- [ ] Requires data directory on base node to be deleted
- [ ] Requires hard fork
- [ ] Other - Please specify

<!-- Does this include a breaking change? If so, include this line as a
footer -->
<!-- BREAKING CHANGE: Description what the user should do, e.g. delete a
database, resync the chain -->
@SWvheerden SWvheerden requested review from a team as code owners April 15, 2024 10:18
@ghpbot-tari-project ghpbot-tari-project added the CR-insufficient_context Your PRs commit messages don't provide enough context to justify accepting the change. label Apr 15, 2024
Copy link

Test Results (CI)

    3 files    120 suites   36m 24s ⏱️
1 268 tests 1 268 ✅ 0 💤 0 ❌
3 796 runs  3 796 ✅ 0 💤 0 ❌

Results for commit a8b7ce2.

@ghpbot-tari-project ghpbot-tari-project added P-acks_required Process - Requires more ACKs or utACKs P-reviews_required Process - Requires a review from a lead maintainer to be merged labels Apr 15, 2024
@SWvheerden SWvheerden merged commit 75bbac1 into tari-project:stagenet Apr 15, 2024
13 of 15 checks passed
@SWvheerden SWvheerden deleted the sw_stag_fixes branch April 15, 2024 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CR-insufficient_context Your PRs commit messages don't provide enough context to justify accepting the change. P-acks_required Process - Requires more ACKs or utACKs P-reviews_required Process - Requires a review from a lead maintainer to be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants