status-go/vendor/github.com/leodido/go-urn/.travis.yml

language: go

go:
  - 1.9.x
  - 1.10.x
  - 1.11.x
  - 1.12.x
  - 1.13.x
  - tip

before_install:
  - go get -t -v ./...

script:
  - go test -race -coverprofile=coverage.txt -covermode=atomic

after_success:
  - bash <(curl -s https://codecov.io/bash)
integrate status-protocol-go 2019-07-17 22:25:42 +00:00			`language: go`

			`go:`
			`- 1.9.x`
			`- 1.10.x`
Move to protobuf for Message type (#1706) * Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage` * Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text. * Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not. * Change the various retrieveX method to a single one: `RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is: `Chats`: -> The chats updated by receiving the message `Messages`: -> The messages retrieved (already matched to a chat) `Contacts`: -> The contacts updated by the messages `RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away. 2019-12-05 16:25:34 +00:00			`- 1.11.x`
			`- 1.12.x`
			`- 1.13.x`
integrate status-protocol-go 2019-07-17 22:25:42 +00:00			`- tip`

			`before_install:`
			`- go get -t -v ./...`

			`script:`
			`- go test -race -coverprofile=coverage.txt -covermode=atomic`

			`after_success:`
			`- bash <(curl -s https://codecov.io/bash)`