This workflow has been disabled for a long time and caused confusion the
other day with Melinda while trying to debug some documentation issue.
Now documentation is published by vercel
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
|
[akhileshns/heroku-deploy](https://redirect.github.com/akhileshns/heroku-deploy)
| action | minor | `v3.13.15` -> `v3.14.15` |
---
### Release Notes
<details>
<summary>akhileshns/heroku-deploy (akhileshns/heroku-deploy)</summary>
###
[`v3.14.15`](https://redirect.github.com/AkhileshNS/heroku-deploy/releases/tag/v3.14.15)
[Compare
Source](https://redirect.github.com/akhileshns/heroku-deploy/compare/v3.13.15...v3.14.15)
- Fix stack issue (courtesy of
[@​sstepanchuk](https://redirect.github.com/sstepanchuk))
- Add dotenv dependency (courtesy of
[@​sstepanchuk](https://redirect.github.com/sstepanchuk))
- Update documentation to more precisely mention that the heroku cli
must be installed
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "after 7pm every weekday,before 5am
every weekday" in timezone Europe/Madrid, Automerge - At any time (no
schedule defined).
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/Unleash/unleash).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xNzYuMiIsInVwZGF0ZWRJblZlciI6IjM5LjE3Ni4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
We already have 20.18.1 set as the default in our Dockerfile, but we
override it with an arg from the workflow, so this brings the workflow
up to date with what we use as our default.
Added more tests around specific plans. Also added snapshot as per our
conversation @gastonfournier, but I'm unsure how much value it will give
because it seems that the tests should already catch this using
respondWithValidation and the OpenAPI schema. The problem here is that
empty array is a valid state, so there were no reason for the schema to
break the tests.
Adds a GH action that notifies us that core features were changed. The
action listens on paths in the source code where our client api and
frontend api are located. If there is a change to these files, we add a
comment to the PR to review carefully and add principals and CTO as
reviewers.
Due to our use of docusaurus and the openapi plugin we need to allow
Artistic-2.0, Having read the license, it allows for free use of the
licensed code, provided the license is included when distributing, but
does not require a relicensing of products using the licensed code.
CC BY 4.0 This license lets others distribute, remix, tweak, and build
upon your work, even commercially, as long as they credit you for the
original creation. This is the most accommodating of licenses offered.
Recommended for maximum dissemination and use of licensed material.
- Sounds compatible with us
So, since we updated to build-push-action@v6 we're now getting a nice
summary of the build on the summary page of the action. It pointed out
that we're caching 0% of our docker build. Since we probably change our
own code more often than we change our dependencies, sharing the initial
yarn install step between builds from cache seems to be a good idea.
<!-- Thanks for creating a PR! To make it easier for reviewers and
everyone else to understand what your changes relate to, please add some
relevant content to the headings below. Feel free to ignore or delete
sections that you don't think are relevant. Thank you! ❤️ -->
## About the changes
When working with automated changes made by the @gitar-bot , custom
automated changes may be necessary. For example,
- Running lint auto-fixes
- Executing code generation
- Updating test snapshot files
- Running internal tools
Gitar recommends these in a separate CI pipeline. We call this [Gitar
Duet](https://gitar.co/docs/more/custom-automated-changes/), where
custom tools run alongside Gitar’s automated changes.
### Important files
github ci workflow files
## Discussion points
Feel free to update the workflow to modify the autofix steps
[](https://renovatebot.com)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
|
[docker/build-push-action](https://togithub.com/docker/build-push-action)
| action | major | `v5` -> `v6` |
---
### Release Notes
<details>
<summary>docker/build-push-action (docker/build-push-action)</summary>
###
[`v6`](https://togithub.com/docker/build-push-action/compare/v5...v6)
[Compare
Source](https://togithub.com/docker/build-push-action/compare/v5...v6)
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "after 7pm every weekday,before 5am
every weekday" in timezone Europe/Madrid, Automerge - At any time (no
schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/Unleash/unleash).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjEuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQyMS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
## About the changes
Small detail I'd like to include which is to copy the changelog from the
release branch to main. This way we'll only have major, minor and patch
logs automatically in main
To help with compliance with customer's OSS requirements, this now bans
usage of GPL and LGPL, as well as scans PRs for dependency
vulnerabilities and new licenses being added.
## About the changes
Summing on Billing page got a little wonky after changing how the
summing worked when the estimation flag is off. This attempts to return
it to previous way of showing numbers when flag is off
If you go directly to the billing page it will not add user calculations
to the total. If you however interact with the UI, like change tabs back
and forth, it will suddenly show the correct sum:
---------
Co-authored-by: Nuno Góis <github@nunogois.com>
Co-authored-by: Gastón Fournier <gaston@getunleash.io>
