Skip to content

chore: merge release into master #4532

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

Merged
merged 14 commits into from
Apr 12, 2019
Merged

chore: merge release into master #4532

merged 14 commits into from
Apr 12, 2019

Conversation

Fatme
Copy link
Contributor

@Fatme Fatme commented Apr 12, 2019

PR Checklist

What is the current behavior?

What is the new behavior?

Fixes/Implements/Closes #[Issue Number].

Fatme and others added 14 commits March 29, 2019 10:30
fix(grunt): generate unit testing dependencies on grunt rebuild command
fix: remove legacy code related to old structure of android project
In case 304 is returned, the cached version of the result should be used, so consider this response as success. NOTE: It can be returned only when specific header is sent in the request, so the caller actually expects to receive either 304 or 200 with new content.
fix: handle HTTP 304 response status code
feat: add sample test in TypeScript for ts projects on test init command
…tructure

fix: support custom tagged android runtime versions
@cla-bot cla-bot bot added the cla: yes label Apr 12, 2019
@ghost ghost assigned Fatme Apr 12, 2019
@ghost ghost added the new PR label Apr 12, 2019
@Fatme Fatme merged commit 3267539 into master Apr 12, 2019
@Fatme Fatme deleted the fatme/merge-release-in-master branch April 12, 2019 11:36
@ghost ghost removed the new PR label Apr 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants