Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(WIP)
tag to today's date inCHANGELOG.md
release
label to this PRChanges
BREAKING: Removed support for
github.com/iver-wharf/wharf-api
v4. Now requires a minimum of wharf-api v5.0.0. (Made wharf-api v5.0.0 compatible #45)Added support for
github.com/iver-wharf/wharf-api
v5.0.0. (Made wharf-api v5.0.0 compatible #45)Changed version of
github.com/iver-wharf/wharf-api-client-go
from v1.3.0 -> v2.0.0. (Updated wharf-api-client-go to v1.3.1 #31, Made wharf-api v5.0.0 compatible #45)Added GitHub's internal project ID when adding project to database. (Made wharf-api v5.0.0 compatible #45)
Added support for the TZ environment variable (setting timezones ex.
"Europe/Stockholm"
) through the tzdata package. (Add tzdata package to prod container #25)Added config loading from YAML files using
github.com/iver-wharf/wharf-core/pkg/config
together with new config models for configuring wharf-provider-github. Seeconfig.go
or the reference documentation on theConfig
type for information on how to configure wharf-provider-github. (Added config and backward compatability #19, Fixed AllowAllOrigins doc comment #29)Added config for setting bind address and port. (Expose bind adress as env var BIND_ADDRESS #14, Added config and backward compatability #19)
WHARF_HTTP_BINDADDRESS
http.bindAddress
Added config for loading extra certificates bundle, in addition to the system's certificates. (Added config and backward compatability #19)
WHARF_CA_CERTSFILE
ca.certsFile
Added logging library
github.com/iver-wharf/wharf-core/pkg/logger
instead offmt.Println
throughout the repository, as well as the Gin integration fromgithub.com/iver-wharf/wharf-core/pkg/ginutil
. (Added wharf-core logging #20)Changed version of
github.com/iver-wharf/wharf-core
from pre release to v1.3.0. (Added config and backward compatability #19, Updated to wharf-core v1.1.0 #28, Changed to use wharf-core/pkg/cacertutil instead of internal/httputils #30, Updated to wharf-core v1.3.0 #43)Changed to return IETF RFC-7807 compatible problem responses on failures instead of solely JSON-formatted strings. (Reworked error output to send IETF RFC-7807 compatible problem responses #16)
Added Makefile to simplify building and developing the project locally. (Added Makefile #24, Fixed make docker-run #26, Fixed Makefile docker build #27, Updated to wharf-core v1.1.0 #28)
Added logging and custom exit code when app fails to bind the IP address and port. (Updated to wharf-core v1.1.0 #28)
Removed
internal/httputils
, which was moved togithub.com/iver-wharf/wharf-core/pkg/cacertutil
. (Changed to use wharf-core/pkg/cacertutil instead of internal/httputils #30)Changed version of Docker base images, relying on "latest" patch version:
Removed
UploadURL
field from theimportBody
struct, and all references towharfapi.Provider.UploadURL
, which will be removed in wharf-api v5.0.0 as it did not provide any functionality. (Removed UploadURL references #35)Changed Dockerfile for easier windows building. (Fix windows docker build #44)
Fixed usage of
git://
URLs when importing and refreshing projects. Since January 11, 2022, GitHub disabledgit://
URLs in favor of onlyhttps://
andssh://
URLs. (Changed to import SSH URL instead #48)Read more here: https://github.blog/2021-09-01-improving-git-protocol-security-github/
Actions after merge
Follow the step-by-step guide found here:
https://iver-wharf.github.io/#/development/releasing-a-new-version?id=merging-a-release-pr